Describe the bug

It is a common convention in rust code to prefix variables with an underscore if unused. When creating a graphql_object, I would like to prototype the interface and keep the compiler happy, so I prefix all the vars with an underscore.

struct Query;
#[juniper::graphql_object]
impl Query {
    fn blah() -> bool {
        true
    }
    fn fizz(_buzz: Strin

xargo CI is failing with a strange ICE:

thread 'rustc' panicked at 'failed to lookup `SourceFile` in new context', src/librustc_middle/ty/query/on_disk_cache.rs:456:17

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpect

error-chain is deprecated and the error types should be migrated to https://github.com/dtolnay/thiserror

I love cargo-watch, and use it on everything! Right now, I am having a bit of trouble figuring out how to ignore a file properly.

The following invocations successfully ignore README.md:

• cargo watch -w src -s "touch README.md"
• cargo watch -i '.md' -s "touch README.md"
• cargo watch -i '*.md' -s "touch README.md"

The following invocations don't ignore README.md, which means

So tarpaulin is in need of some more tests. Currently I'm relying on a small number of tests and doing informal runs of projects to test things but as more features get added on this becomes harder to do.

There are a few areas I'd like to tackle, if anyone chooses to help I'm willing to help mentor you through any issues and generally help out.

Integration tests

• Test tarpaulin on run

Is there a description somewhere, in the rust docs, rfc, something..? that explains what exactly is necessary to do a cross build, or do I have to reverse engineer sysroot.rs?

Adding documentation example of a working CI build using cirrus-ci.org (.cirrus.yml)

This is something that hasn't been super clear to me, and I haven't really seen it discussed anywhere ever.

The corpus

• can end up getting sizable (see also #163)
• often isn't human readable

Committing it to the project-being-fuzzed's repo seems like it could add a bunch of git overhead and even make merges difficult.

But, it is needed to "pick up where you left off" when doing time

The suggestion original line snippets are missing the first character on multiline fixes.

For example, a clippy warning about a redundant return at https://github.com/facebookexperimental/eden/blob/139717db04a9a28fca7f3d81553275198bbbb8a1/eden/mononoke/sshrelay/src/lib.rs#L165
shows a fix with the original text:

return Err(io::Error::new(\n                       io::ErrorKind::InvalidInp

Currently, when the no-dev-version configuration parameter is set to false (which is the default), it is possible to use the --no-dev-version CLI argument to override it to true. However, the reverse operation is not supported: if no-dev-version is set to true in the configuration, there is no CLI argument that can override it to false. It would be nice to add a flag (--dev-version? `--for

so i found out i can disable

• language-rust
• terminal-plus
• build-cargo

but not

• linter-rust

by trial and error. it would be nice to have this on the webpage or readme

When adding a license exception, you must enumerate each allowed license needed to satisfy the expression for the crate, even ones that are already allowed globally. Instead, the allowed list should just be additive to any existing global license setting.

See #119

ssokolow@monolith rdbackup-excludes-indexer [master] %% cargo profiler     
error: Invalid profiler. cargo profiler currently supports callgrind and cachegrind.

Referring to "no profiler" as an invalid profiler is one of those things that only makes sense to a computer.

The error message should be one of the following in this case:

• error: You must specify a profiler.

Someone on reddit points out that we should work even if the system python points to 3, as long as there's a python2 or python2.7 installed.

Issue: the only line in the whole readme that shows how to execute dinghy is the very last line that states cargo dinghy test.

• First: add a table of contents.

• Second: add a quick start guide, with two self contained examples, one for ios and one for androd that shows how to get the tests of a very basic Rust project to run. By self contained I mean that somebody that does this

rustfmt messages usually starts with line similar to this:

Diff in /home/runner/some/random/path.rs at line 135:

We could probably add the problem matcher similar to rust one to highlight them, so it would be easier to read logs.

Thing to check: would it be possible to "enable" this matcher only if `cargo f

This is a tracking issue for additional Indexer implementations.

Here is a non-exhaustive list of potential candidates for an Indexer implementation:

• RemoteIndex:
  Requires to implement a companion server.
  The idea is to have a clone of the index on another machine on which a companion server is running, you would then point Alexandrie to that server and it would take care o

Optional dependencies should not be treated as a "dependency" kind, of which there are only three -- regular, build, and dev. "Optional deps" should instead be handled as a boolean flag, which is what cargo does. A dependency can be both a build dependency and optional simultaneously, but currently cargo-deps will erase one of these.

Optional dependencies can be displayed with a dashed line.