cargo-semver-checks Crash Report (after using absolute path to dependency, panic: "we declared a dependency on a crate that doesn't exist in the metadata") #476
Labels
C-bug
Category: doesn't meet expectations
Steps to reproduce the bug with the above code
Hi! The program told me to submit the attached file. This is running on
arti
, comparing it against a branch containing the previous version (with light hacking to work around a bug that causes the previous version not to compile correctly because of a pinned dependency which has been yanked.)I suspect that this behavior is at issue. To work around the release bug here, I had to hack together a fake version of one of our upstream dependencies, and use
dependencies.x.path
in one of our crates to use the hacked-up version.To work around the fact that cargo-semver-checks builds in a subdir, I had to use an absolute path to my hacked-up crate. I think this might be the problem.
I've tried to come up with a smaller reproducer, but it didn't seem to work.
Actual Behaviour
Here is my interaction with the program.
Here are the contents of the report-xxx.toml file; I'm pasting it here because github doesn't want me to upload toml.
Expected Behaviour
.
Generated System Information
cargo version
Compile time information
The text was updated successfully, but these errors were encountered: