"Could not find requested crate" unless I revert to the git index #641
Comments
|
I think we need to update Cargo to a version that defaults to the sparse index. |
|
is it better in 0.25? |
|
There doesn't seem to be a |
|
I've updated to |
|
Oh, and in case it's useful, here are the dependency versions the install used (retrieved from |
|
Ok, I was able to reproduce it. There must be something wrong in our Cargo integration. The workaround is to add the crate you want as a dependency and run |
|
(This comment is only to provide use-case context.)
Indeed that would also be more convenient. The reason I don't is that the goal I am working towards is “not personally vulnerable to malware in packages”, so I'm practicing a workflow that doesn't run any of the code before I've reviewed it, and having it set as a dependency makes it much more likely to be run (certain, if rust-analyzer is open on the package with the dependency). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I attempted to begin a review:
On a suspicion that the problem has to do with Cargo's new sparse index protocol, I tried:
and it succeeded. So, it seems that
cargo-crevis making some assumption that depends on the old protocol.crev:cargo installThe text was updated successfully, but these errors were encountered: