Skip to content
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

Closed
AxelThePop opened this issue Dec 27, 2024 · 5 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@AxelThePop
Copy link

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

@AxelThePop AxelThePop changed the title "error decoding response body" When "uv self update" "error decoding response body" when "uv self update" (uv version: 0.5.12) Dec 27, 2024
@monk-time
Copy link

monk-time commented Dec 27, 2024

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.

@charliermarsh
Copy link
Member

Sorry -- this is a bug in reqwests that I fixed last night (#10187), but didn't realize that the subsequent release failed. I'll get it out now.

@charliermarsh
Copy link
Member

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.).

@charliermarsh charliermarsh self-assigned this Dec 27, 2024
@charliermarsh charliermarsh added the bug Something isn't working label Dec 27, 2024
@charliermarsh
Copy link
Member

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 uv self update:

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.

@AxelThePop
Copy link
Author

Well done!
success: Upgraded uv from v0.5.12 to v0.5.13! https://github.com/astral-sh/uv/releases/tag/0.5.13
success: You're on the latest version of uv (v0.5.13)

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants