Jake Shadle

@supervacuus Nope, we rewrote everything in Rust so we have full control https://github.com/rust-minidump/minidump-writer

I just realized this was resolved in #533, the clarification can provide any path it wishes as long as it is contained in the package source.

We don't compile physx for wasm ourselves but we'll gladly take patches that add/fix support that include CI to ensure it doesn't break in the future.

I'd accept a PR for this, but won't do one myself, at least in the foreseeable future. I think the easiest would just be a new option `--debug-dylibs ` that...

The purpose of this tool is not to replace Microsoft's bloated installer, only to get the minimal things needed to seamlessly cross-compile and link a Windows executable. I don't know...

Most config options have a default lint level that matches the default config that gets generated if you don't have one already or you run init. You can either edit...

I am not sure that this makes sense for cargo-deny. It is an extremely specific case that seems like it would be easier to verify by using `--locked` and validating...

You can't currently only check normal dependencies when checking for bans.

Test suites are outputted as a single block to match libtest, eg. ``` {"type":"suite","event":"started","test_count":} {"type":"test","event":"started","name":} ... {"type":"test","event":"ok","name":,"exec_time":0.009431065} ... {"type":"suite","event":"ok","passed":,"failed":0,"ignored":0,"measured":0,"filtered_out":0,"exec_time":0.150101485} ``` But nextest executes tests much differently so that matching libtest...

Well, works as in, all tests pass locally for me, I have no idea why relay_routing fails in CI.