-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 build giving checksum mismatch error #13414
Comments
$ rustup --version INNEBIS1@IN-L-7402183 MINGW64 /d/eventgrid_project/rust_project (master) |
It seems you'v configured source replacement (a.k.a. mirrors). Check your |
@weihanglo I just installed Rust and created new project using "cargo new project-name" cli and executed "cargo build". |
If you look in your cargo.lock for the section about autocfg v0.1.8, what is there? |
Cargo's error for this case will indicate source replacement even when it's not explicitly configured due to the built-in sparse replacement of crates.io, so it's possible that no source replacement is configured here. I just opened #13433 to improve the errors. Can you check if Another way to check (if you have nightly available) is to run |
~/.cargo/registry/cache/index.crates.io-6f17d22bba15001f/autocfg-0.1.8.crate it is not created for me. |
There is no cache folder present under ~/.cargo/registry INNEBIS1@IN-L-7402183 MINGW64 ~/.cargo/registry INNEBIS1@IN-L-7402183 MINGW64 ~/.cargo/registry Rather I have below file present for autocf. $ cat ~/.cargo/registry/index/index.crates.io-6f17d22bba15001f/.cache/au/to/autocfg |
The error you're getting "failed to verify the checksum of |
|
I'm going to close due to inactivity. Feel free to reopen if you have run possible workarounds above and had new findings to share. |
Problem
Hi All,
I have cargo.toml file present in windows 11 machine where trying to use rumqtt 0.31.0 version.
But when i am running "cargo build" cli, I'm getting below error:
can anyone please help me with this error.
Steps
steps:
Possible Solution(s)
No response
Notes
No response
Version
No response
The text was updated successfully, but these errors were encountered: