-
Notifications
You must be signed in to change notification settings - Fork 912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"error decoding response body" when "uv self update" (uv version: 0.5.12) #10191
Comments
This seems pretty serious. If v0.5.12 broke all network requests and it can no longer self update to v0.5.13 that contains a fix for that, how can all v0.5.12 users upgrade to it? ISTM v0.5.12 should be recalled as soon as possible and instructions for alternative updating route should be made highly visible. Also it seems strange how testing didn't catch a breakdown of such core functionality as networking. |
Sorry -- this is a bug in |
The reason it wasn't caught in testing is that it's specific to specific registries. All the reports in #10190 are from custom registries (like CodeArtifact, Gitlab, etc.). |
This should be fixed in v0.5.13. If you're on v0.5.12, you may need to reinstall with cURL rather than via curl -LsSf https://astral.sh/uv/install.sh | sh Sorry for the inconvenience! It's my mistake for going to bed without double-checking the release pipeline. |
Well done! Thanks. |
I've updated to the "0.5.12 (351d602 2024-12-26)" with "uv self update". If I hit "uv self update" now, I get:
"error: error decoding response body
Caused by: there are extra bytes after body has been decompressed"
Windows 10 with all the latest updates, Powershell 7.4.6
The text was updated successfully, but these errors were encountered: