-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo-outdated panics if an git url with ssh is specified #195
Comments
Hello @Marwes thanks for reporting this issue! This was resolved in #182 and is the current master branch but was not tagged/released via Crates.io yet (which would be One thing I noticed in the example you provide is the dependency section should be like so:
If you have Here's an example of the output using the
|
It was just a minimal reproduction from a larger file, I just wrote the first repo I could think of in there and it was enough to reproduce :). It does not appear to be fixed on master. Did |
Oh, that's really strange this happens if you install it to |
FYI, I put in the above work in progress PR to rust-lang/cargo after finding the root cause. Hopefully, this could get rolled out shortly. |
We pushed a new lock file to master today ( To resolve while we wait for the workaround in
|
…re users are using the resolution to kbknapp#195)
Updated install instructions to lock the dependency tree (and make sure users are installing the fix for #195)
Running
cargo outdated
on a crate with the followingCargo.toml
results in a panic.The text was updated successfully, but these errors were encountered: