Rain

(Definitely something I still want, but toml 0.5 has been trucking along so it hasn't been a huge priority for me)

Thanks for the report! This seems like a good idea. The way I'd probably do this is: currently, setup scripts are either pass or fail. We'd want to add a...

Thanks for the report -- this change was inherited from a cargo_metadata update to 0.20.0 which started requiring that package names be non-empty. I'd recommend trying to update your Rust...

(This was not documented in the nextest changelog -- my oversight -- but it is documented at https://github.com/guppy-rs/guppy/blob/main/guppy/CHANGELOG.md#changed. In my testing, the bindeps feature no longer produces empty package names.)

It's definitely from cargo_metadata and specifically this field being validated: https://docs.rs/cargo_metadata/0.20.0/cargo_metadata/struct.NodeDep.html#structfield.name Please follow up with upstream cargo_metadata.

The JSON snippet that's failing to parse: ``` "deps":[{"name":"","pkg":"path+file:///home/rain/dev/tmp/nextest-repro-2407/subcrate#0.1.0","dep_kinds":[{"kind":"build","target":null,"extern_name":"subcrate","artifact":"bin","bin_name":"subcrate"}]}],"features":[]} ``` The `"name":""` is what's at issue.

(Honestly I think this is a bug in Cargo. Not clear to me why it's producing an empty name there — it makes it hard to match up the deps...

Looks like the restriction on empty dependency names has been lifted. I'll update dependent crates this weekend.

@benbrittain yep, see https://github.com/guppy-rs/guppy/pull/524.

This is now out in cargo-nextest 0.9.101, which will make its way to crates.io within roughly 20 minutes.