Martin Pool

It looks like it's still happening, from a similar command /home/mbp/.rustup/toolchains/beta-x86_64-unknown-linux-gnu/bin/cargo nextest run --package cargo-nextest --package integration-tests --package nextest-filtering --package nextest-metadata --package nextest-runner However strangely when I run that outside...

I'm going to unassign and deprioritize this for now because while it _might_ be pointing to a bug in cargo-mutants or a failure to handle some reasonable behavior, it also...

At least as a workaround you should be able to use `--cargo-arg --target-dir=D`, or `-C` for short.)

I did try that but I think it's worth another go. In general, falling back to regexps has the same problem with matching using regexps rather than semgrep: unwanted sensitivity...

What I ended up with is ```yaml --- rules: # This generates a deprecation warning in Terraform >0.11; this rule is here mostly so that # we can autofix it....

Looking at the code, I think the problem is that the environment variable is only read by the `FailScenario` constructor, so binaries that just directly have failpoints won't ever fail....

Would you be open to a PR that mentions in the `cargo package` and `cargo publish` docs that symlinks are followed and symlinks are never(?) included in the tarball?

Specifically the problem seems to come from the combination of 1. Using the `JsonSchema` derive macro. 2. Having a docstring containing the sequence `--`. (jsonschema extracts the docstrings into metadata,...

I got a backtrace in case that helps: ``` stack backtrace: 0: __rustc::rust_begin_unwind at /rustc/573a01569000d395498a5f98f916d6e5305ac81a/library/std/src/panicking.rs:697:5 1: core::panicking::panic_fmt at /rustc/573a01569000d395498a5f98f916d6e5305ac81a/library/core/src/panicking.rs:75:14 2: core::panicking::panic_display at /rustc/573a01569000d395498a5f98f916d6e5305ac81a/library/core/src/panicking.rs:268:5 3: core::panicking::panic_explicit at /rustc/573a01569000d395498a5f98f916d6e5305ac81a/library/core/src/panicking.rs:241:5 4: hir_expand::builtin::fn_macro::concat_expand::panic_cold_explicit at...

And it seems to be coming from this `concat!` call, probably: https://github.com/GREsau/schemars/blob/e4653c7c738299ca865269970ec1aad6b77f6a01/schemars_derive/src/attr/doc.rs#L5-L37