-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 Can't update crates.io Index #7662
Comments
Thanks for the report! Do you have a firewall, proxy, or any other sort of network configuration setting in effect? |
You can also try setting the environment variables |
@alexcrichton - My organization does install Umbrella Roaming Client on all our laptops, however, github is not blocked, the settings have remained the same, cargo's worked without error with it in the past. I checked, and I'm able to clone the repo, curl it, or visit it online. Strange. @ehuss - I set both of those variables and tried a few commands, but the output remained the same. I'm starting to suspect the zlib might be the issue after all. If that's the case, is there anyway to update it, or check that it's fully functional? |
Looking through cargo's code, I found a few potential causes for this error. in
Unfortunately, I wasn't able to find the exact cause of this error - I suspect it has to do with the TL;DR: Issue was resolved by clearing the contents of the cargo registry folder (& the cargo git cache). See #5101. |
This PR enables debug logging on requests from cargo to the registry in semver-checks action (rust-lang/cargo#7662 (comment)). Hopefully, it will let us debug the network issue reported here: #3782 (comment) Pull-Request: #3838.
Cargo's worked for me in the past, but for some reason it stopped working today. I haven't done anything recently (that I can see) that would cause this behaviour, so I'm fairly puzzled. Here's the minimum required to encounter this error on my machine:
Start a new project, and add a dependency to
cargo.toml
:(The package doesn't matter, the error is the same no matter what.)
upon running
$ cargo run
(or any command that requires crates to be fetched), I encounter the following error:At first, I thought I might have a problem with
zlib
, but this doesn't seem to be the case.I updated Rust & Cargo, but nothing changed.
(I'm running
cargo 1.39.0 (1c6ec66d5 2019-09-30)
onMacOS Catalina 10.15
)If you have any idea as to what's going on (is it my machine?, a cargo bug? zlib?) please don't hesitate to leave a comment 😄.
The text was updated successfully, but these errors were encountered: