You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have a workspace with a binary crate and another crate declaring a dependency on that binary crate (notwithstanding whether that makes sense), cargo metadata outputs a depedency with name null. Since cargo-metadata expects dependencies to always have a name, it fails to deserialize that metadata.
I mentioned this here, and have a PR to change it on the Cargo side (rust-lang/cargo#6534). However, there is some minor disagreement on how it should be fixed.
If I have a workspace with a binary crate and another crate declaring a dependency on that binary crate (notwithstanding whether that makes sense),
cargo metadata
outputs a depedency with namenull
. Sincecargo-metadata
expects dependencies to always have a name, it fails to deserialize that metadata.Here's a minimal reproduction: https://github.com/flodiebold/cargo-metadata-bug
The text was updated successfully, but these errors were encountered: