Installing packages from custom pypi server fails on 0.1.32

[bnaul]

Highly likely that the root issue is on our end but figured it's still worth an issue since others might be facing the same issue soon: upon upgrading to uv==0.1.32, our docker builds started failing with

error: HTTP status server error (502 Bad Gateway) for url

Rolling back to 0.1.31 fixed things.

We UV_INDEX_URL=... pip install -r requirements.txt with a couple (3?) of packages coming from a self-hosted pypiserver instance, and the rest (400?) are publicly available on PyPI. No obvious issues with the health of our server, CPU load is still extremely low, can't find anything noteworthy in the logs.

I git bisected my way to #2817 and found that any commits before this change succeed. That's about all I've been able to find but if there's any other uv or pypiserver output that would be of interest let me know and I'll post it!

[zanieb]

Hey Brett! Good to see you.

Sorry this issue fell through the cracks, are you still encountering this on the latest version? I think a lot changed in our network stack with #2817, seems possible we made a mistake or that there's a regression upstream.

[bnaul]

Hi @zanieb 👋 yes, I just checked and we still encounter this on 0.1.36. Don't have many other details to share but a couple other things:

• uv pip install <a few packages> works fine, it's only installing our full set of requirements that triggers the issue
• uv pip compile also reliably triggers the issue for su

[zanieb]

FWIW we've used pypiserver for some testing and I've seen pretty consistent errors at high levels of parallelism. We may just need to let people turn down our network concurrency.