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
Error: The repo at path /home/gabor/.cargo/registry/index/github.com-1ecc6299db9ec823 is unusable
due to having an invalid HEAD reference: reference 'refs/heads/main' not found; class=Reference (4);
code=NotFound (-3)
Apparently this was caused by me Ctrl-C-in a previous run of cargo-upgrade upgrade that seemed to have been stuck (not showing anything for more than a minute) After removing that folder and running cargo-upgrade upgrade again (and Ctrl-C-ing again) I get the same error.
The text was updated successfully, but these errors were encountered:
This happened to me today too. See #869, #841. A workaround is described in #869. I fixed this for myself by:
blowing away my entire Cargo registry (by removing .cargo/registry entirely, but importantly NOT the rest of .cargo) (this might not be the smartest way to get back into a good state, but I didn't really feel like figuring out how to fix my existing .cargo/registry in-place, and I'm not sure it matters much*)
CARGO_REGISTRIES_CRATES_IO_PROTOCOL=git cargo fetch
CARGO_REGISTRIES_CRATES_IO_PROTOCOL=git cargo upgrade # <-- you might not need to use the env variable here, since the repo will exist after the last command
* If I'm reading the issues right, I am pretty sure the issue only occurs when you have a cargo install that has only ever used sparse checkouts - so you're probably not deleting any data that would take a long time to re-fetch. The cargo fetch in step 2 will still take a long time. But if the problem is as described in the issues listed above, you wouldn't have had that data locally in the first place.
When I run
cargo-upgrade upgrade
I get:Apparently this was caused by me Ctrl-C-in a previous run of
cargo-upgrade upgrade
that seemed to have been stuck (not showing anything for more than a minute) After removing that folder and runningcargo-upgrade upgrade
again (and Ctrl-C-ing again) I get the same error.The text was updated successfully, but these errors were encountered: