Open bewinsnw opened 1 month ago
I have a potential fix for this, which also addresses #4 (it is the same issue I believe).
I'm just waiting on this to be reviewed, but there is a chance it will be delayed a bit due to holidays.
I think this is fixed with v0.6.0. Would you mind taking a look and reporting back? (it should be possible to get a range if the upstream server supports it)
If you try proxying to pypi and attempt to install jinja with
uv
against this server, uv will crash.This is because the headers streamed from pypi: https://github.com/simple-repository/simple-repository-server/blob/fe353669c64ca77ef9621d377bb728a13e6c33ae/simple_repository_server/routers/simple.py#L151
... include "accept-ranges: bytes", which uv takes as being true and then tries to use to fetch metadata from wheels.
I fixed this in my copy with:
It'd be better if we could pass the ranges in the request to the back end, but it all works. The reason why uv is making these range requests is because it didn't understand the "core-metadata" attribute from PEP-714: I recently asked Charlie to fix this so it should be in the next release https://github.com/astral-sh/uv/issues/3689