XAMPPRocky

@rbtcollins Yes that would be greatly appreciated, as it's a lot easier to fit code reviews into my schedule than coding time.

FWIW I'm using a `release-plz` which uses `cargo-semver-checks` for version bumps, and this missing lint is the most often occurring bug we have with using `cargo-semver-checks` for octocrab

> This is probably not what you wanted to hear, and I am sorry about that. Oh not at all, as another open source maintainer I very much understand the...

FWIW since it is a macro, you could always add an additional argument to the macro that accepts a `Settings` type, this would keep it being compatible with `std::assert_*` but...

This is the code I ended up using , I had to assume a default path of `/entrypoint.wasm` because I couldn't figure out a way to create an image with...

I should note this is with a single entry in the map, it gets worse as the map gets larger.

I think the fix here is for `cargo-instruments` to recognise when it's being terminated from the `CTRL+C` signal, and to finish writing the traces file. Without that you can't really...

> The problem is that we aren't responsible for writing traces; that's up to xctrace, and so we have no control over what it does in response to SIGINT. Right...

Still an issue.

still an issue