-
Notifications
You must be signed in to change notification settings - Fork 46
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
Sometimes fails to load save analysis for crates with no dependencies #103
Labels
bug
Something isn't working
Comments
This started happening consistently to me too. It is also for edition 2021 crates. |
Any steps to consistently reproduce it would be really neat, then I could try to figure out the cause. Thanks! |
For what it's worth, we are also running into this issue as well :( |
benesch
added a commit
to benesch/materialize
that referenced
this issue
Feb 19, 2022
But mark it to soft fail. I think the failures we were seeing before might be an upstream bug for which there is no known workaround. See: est31/cargo-udeps#103.
2 tasks
we are having the same issue :( |
wangandi
pushed a commit
to wangandi/materialize
that referenced
this issue
Apr 11, 2022
But mark it to soft fail. I think the failures we were seeing before might be an upstream bug for which there is no known workaround. See: est31/cargo-udeps#103.
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a workspace that contains a crate with no dependencies, which is depended on by a few other crates in the same workspace. Running
cargo udeps
in the workspace sometimes results in the following error:As an workaround, adding an arbitrary dependency to the problematic crate temporarily resolves the problem, until it's removed. Running
cargo clean
beforecargo udeps
does not seem to have any effects.cargo-udeps
is compiled from commitdece8b2
. The crates are in edition 2021. I haven't been able to reproduce the problem with a fresh workspace, unfortunately.The text was updated successfully, but these errors were encountered: