Rust update broke all of my projects. Cannot build due to `spurious network error`

[Nordgaren]

I tried this code:

building my project
https://github.com/Nordgaren/pe-util
https://github.com/Nordgaren/memory-mirror
https://github.com/Nordgaren/fisherman
https://github.com/Nordgaren/tabstate-util

The list goes on

I expected to see this happen: explanation

I expected it to build

Instead, this happened: explanation

Execution failed (exit code 101).
C:/Users/Nordgaren/.cargo/bin/cargo.exe metadata --verbose --format-version 1 --all-features --filter-platform x86_64-pc-windows-msvc
    in working directory: C:\Users\Nordgaren\source\Rust\pe-util
    with extra environment variables: CARGO_TERM_PROGRESS_WHEN=always TERM=ansi RUSTC=C:\Users\Nordgaren\.cargo\bin\rustc.exe RUST_BACKTRACE=short CARGO_TERM_PROGRESS_WIDTH=80
stdout:     Blocking waiting for file lock on package cache
    Updating git repository `https://github.com/Nordgaren/encoded-pointer.git`
warning: spurious network error (3 tries remaining): failed to send request: A connection with the server could not be established
; class=Os (2)
warning: spurious network error (2 tries remaining): failed to send request: A connection with the server could not be established
; class=Os (2)
warning: spurious network error (1 tries remaining): failed to send request: A connection with the server could not be established
; class=Os (2)
error: failed to get `encoded-pointer` as a dependency of package `pe-util v0.1.0 (C:\Users\Nordgaren\source\Rust\pe-util)`

Caused by:
  failed to load source for dependency `encoded-pointer`

Caused by:
  Unable to update https://github.com/Nordgaren/encoded-pointer.git#010e735c

Caused by:
  failed to clone into: C:\Users\Nordgaren\.cargo\git\db\encoded-pointer-22d63338fdd0644f

Caused by:
  failed to send request: A connection with the server could not be established
  ; class=Os (2)

stderr: 

Meta

rustc --version --verbose:

rustc 1.80.1 (3f5fd8dd4 2024-08-06)
binary: rustc
commit-hash: 3f5fd8dd41153bc5fdca9427e9e05be2c767ba23
commit-date: 2024-08-06
host: x86_64-pc-windows-msvc
release: 1.80.1
LLVM version: 18.1.7

I don't have a backtrace because I can't even build the projects.

This happend one day after updating rust.
If I go back to an older version of Rust, like 1.75.0, they build fine and don't have this error. I have no idea what I need to do to "Upgrade" my tools, but I keep getting DMs telling me my code doesn't work because other people are apparently having this issue, as well, on newer compiler versions.

What do I need to do? I tried uninstalling Rust completely and re-installing, and that didn't work. I would really like my tools to not be stuck on an old version of Rust for something that seems like it has nothing to do with me.

My tools are just hosted on GitHub, because most of them are not ready.

[Nordgaren]

Here is the encoded-pointer crate that the message mentions : https://github.com/Nordgaren/encoded-pointer

This crate builds, but it has no dependencies, so it doesn't need to try to download anything.

[ryanavella]

Are you behind a corporate or university proxy, or using a VPN or similar? This seems more like a cargo issue than a rustc issue, possibly related to #6513. Some users in that thread shared fixes that worked for them.

Note that your diagnostic says it is trying to fetch commit 010e735c of encoded-pointer, which suggests your Cargo.lock is out of date. Though I don't think this is related.

[Nordgaren]

I am just on my home internet, no VPN. Nighthawk router, and it hasn't changes recently, or been reset or anything. If I change back to rust 1.75.0, it works just fine. It builds the project with no issues.

[workingjubilee]

Hm, so, I cloned the pe-util repository, set rustup default stable, and then ran cargo build.

It built fine:

$ cargo build
    Updating git repository `https://github.com/Nordgaren/encoded-pointer.git`
     Locking 2 packages to latest compatible versions
   Compiling encoded-pointer v0.1.0 (https://github.com/Nordgaren/encoded-pointer.git#dc0f551a)
   Compiling pe-util v0.1.0 (/home/jubilee/rust/nordgaren/pe-util)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.01s

[Nordgaren]

Hm, so, I cloned the pe-util repository, set rustup default stable, and then ran cargo build.

It built fine:

$ cargo build
    Updating git repository `https://github.com/Nordgaren/encoded-pointer.git`
     Locking 2 packages to latest compatible versions
   Compiling encoded-pointer v0.1.0 (https://github.com/Nordgaren/encoded-pointer.git#dc0f551a)
   Compiling pe-util v0.1.0 (/home/jubilee/rust/nordgaren/pe-util)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.01s

Encoded pointer is literally the only crate here that builds fine...

From my earlier post...

Here is the encoded-pointer crate that the message mentions : https://github.com/Nordgaren/encoded-pointer

This crate builds, but it has no dependencies, so it doesn't need to try to download anything.

[saethlin]

Encoded pointer is literally the only crate here that builds fine...

Jubilee demonstrated building pe-util, not encoded-pointer.

I can build all of your projects just fine (or at least get past the stage where Cargo has downloaded everything it needs), even if I wipe the entire Cargo registry directory, which would force Cargo to do as much network activity as possible.

[Nordgaren]

Sorry, I am really tired. I misread your message. For some reason I just saw encoded pointer.

The last report I got from someone else was from this repo https://github.com/Nordgaren/dll-proxy
and it was the same issue.

I re-installed everything from scratch with rustup. Is there anything else I can check or delete to get the index to refresh or something

[saethlin]

Is there anything else I can check or delete to get the index to refresh or something

You can purge the downloaded registry state by deleting the .cargo/registry directory. It should be one folder up from where the Cargo executable is.

[Nordgaren]

It's just really strange to me that I can go back to 1.74.0 and it works fine. I can even do cargo update and it pulls it down. As soon as I update, it does this.

Should it be checking crates.io for a crate that's specified to be on git?

[saethlin]

Cargo is trying to generate its lockfile. It needs to find out which commit hash it is going to build with, because you didn't specify one in the Cargo.toml, or check in a Cargo.lock.

Everything except registry dependencies are somewhat oddly-behaved in Cargo.

You say backing up to 1.74. Does 1.79 work?

[Nordgaren]

Yea, that all got deleted when I did rustup self uninstall, but just to be sure, I just deleted it, and had the same error. After deleting it all I got was a CACHEDIR.TAG that had this in it

[Nordgaren]

Yes, 1.79 builds