Repeated timeouts in GitHub Actions fetching wheel for large packages

[adamtheturtle]

In the last few days since switching to uv, I have seen errors that I have not seen before with pip.

I see:

error: Failed to download distributions
  Caused by: Failed to fetch wheel: torch==2.2.1
  Caused by: Failed to extract source distribution
  Caused by: request or response body error: operation timed out
  Caused by: operation timed out
Error: Process completed with exit code 2.

I see this on the CI for vws-python-mock, which requires installing 150 packages:

uv pip install --upgrade --editable .[dev]
...
Resolved 150 packages in 1.65s
Downloaded 141 packages in 21.41s
Installed 150 packages in 283ms

I do this in parallel across many jobs on GitHub Actions, mostly on ubuntu-latest.

This happened with torch 2.2.0 before the recent release of torch 2.2.1.
It has not happened with any other dependencies.
The wheels for torch are pretty huge: https://pypi.org/project/torch/#files.

uv is always at the latest version as I run curl -LsSf https://astral.sh/uv/install.sh | sh. In the most recent example, this is uv 0.1.9.

Failures:

• https://github.com/VWS-Python/vws-python-mock/actions/runs/8017894929/job/21902693117
• https://github.com/VWS-Python/vws-python-mock/actions/runs/8000017693/job/21848747452
• https://github.com/VWS-Python/vws-python-mock/actions/runs/8000017693/job/21848749557

[adamtheturtle]

Perhaps I just need to use UV_HTTP_TIMEOUT and I will, but I thought that this might be worth pointing out:

• If so, the error message could helpfully point to UV_HTTP_TIMEOUT
• Perhaps the default is too small if using GitHub Actions + a popular package times out

[zanieb]

Thanks for the feedback, I've opened issues for your requests

• Increase or adjust scope of default HTTP timeout #1921
• Display HTTP timeout setting on timeout #1922

[adamtheturtle]

Thank you @zanieb ! I don't know the value of having this issue open, but I'll leave it to you to close if desired.

[zanieb]

In #1921 my co-worker noted that this might be a bug in the way we're specifying the timeout so I'll recategorize this one and leave it open.

[konstin]

Looking at the actions runs, all the passing actions take ~30s, while the failing ones error after 5min, which is our default timeout, so this looks like a network failure (in either github actions or rust)

[konstin]

I'm not seeing any timeouts anymore with the two most recent versions (https://github.com/konstin/vws-python-mock/actions). Could you check if this now solved?

[adamtheturtle]

I have not seen this issue since posting. Thank you for looking into this.

[konstin]

I'll close it for now, please feel free to reopen should it reoccur