Rain

This is really tricky to do correctly with clap currently. I think I'm going to defer this. As a compromise, I've added `cargo nextest r` as an alias to `cargo...

So adding the terminal to Developer Tools [as documented here](https://nexte.st/book/antivirus-gatekeeper.html#how-to-add-your-terminal-to-developer-tools) is supposed to prevent that kind of hash-based check from happening. I'm not sure why it's not working for you....

Going to reopen this, since I think it's desirable eventually once clap has better support for it (https://github.com/clap-rs/clap/issues/975).

I can't repro this on my remote M1 Mac Mini with Monterey 12.5.1. I ran on your repo: ``` cargo clean cargo nextest run --no-run --all cargo nextest list --all...

Sadly macOS is just really janky and buggy in my experience, and its closed source nature makes it hard to tell what's going on. I've tried working with an Apple...

re grcov: So I'm not sure how it works, but my suspicion is that the fact that nextest runs tests in parallel might be causing test coverage data to clobber...

Thanks, it looks like the ctrl-c needs to be forwarded from nextest to child test processes, similar to how signals are forwarded on Unix. The code for that just hasn't...

So looking at your test further, I'm now less sure of what's going on. It looks like the test sends ctrl-c to itself (which is fine) but for some reason...

Huh, that's really strange. So it's specifically the fact that nextest redirects standard output that causes it? I don't quite understand, to be honest! It may be worth spending some...

Hi there— I love feature-powerset and use it for some of my own crates, so I feel the pain you have here. Sadly, I can't think of any easy fixes...