crates.io responded with 500 instead of 200 when downloading crate

[Mark-Simulacrum]

Possibly just network failure (#40474), but we did get some response, so presumably not that.

First instance here: #41332 (comment).

Log from that:

error: unable to get packages from source
Caused by:
  failed to get 200 response from `https://crates.io/api/v1/crates/utf8-ranges/0.1.3/download`, got 500
thread 'main' panicked at 'tests failed for https://github.com/BurntSushi/xsv', src\tools\cargotest\main.rs:78
note: Run with `RUST_BACKTRACE=1` for a backtrace.
command did not execute successfully: "C:\\projects\\rust\\build\\x86_64-pc-windows-msvc\\stage0-tools\\x86_64-pc-windows-msvc\\release\\cargotest.exe" "C:\\projects\\rust\\build\\x86_64-pc-windows-msvc\\stage0/bin\\cargo.exe" "C:\\projects\\rust\\build\\ct"
expected success, got: exit code: 101

[alexcrichton]

Ah yeah I've been lumping these in with #40474, there's been a few others of these from time to time.

[carols10cents]

FWIW I just tried to search in crates.io's logs for utf8-ranges/0.1.3 with status 500 and I didn't see anything... wonder if that was from S3....?

[alexcrichton]

@carols10cents oh I was investigating this a long time ago and ended up reaching the same conclusion, that the 500 code was from S3. I think that's a normal ocurrance.

The "solution" here is to likely bake in an auto-retry into Cargo itself when it gets a 500 from S3 which is even officially recommended

[carols10cents]

It looks like cargo has network retry logic but it's only being used for git sources? I'm going to file an issue for using that logic for other sources as well

[alexcrichton]

Oh Cargo has retry logic for the registry, it just only retries if the error claims its spurious and a 500 isn't a curl::Error but rather is checked just below.

I think we'd just need to tweak the retry logic here.

[carols10cents]

oooooohhhh. Yeah was just coming to the conclusion that with_retry IS being used for all sources. Will change what bug I'm filing to be about tweaking the retry logic :)

[carols10cents]

Issue filed! rust-lang/cargo#3962

[Mark-Simulacrum]

In theory this was solved upstream, and either way, closing in favor of #42118.