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 resolving dependencies from aws codeartifact repo since 0.5.12 #10190

Closed
okan-agca-entrix opened this issue Dec 27, 2024 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@okan-agca-entrix
Copy link

Hello,
I'm encountering a new error since upgrading to 0.5.12 while running uv sync. The setup is described below. The error is not present with version 0.5.11 of uv. If there are migration steps I missed, would be happy if you can direct me there. Had a brief look at the release notes but didn't see anything relevant.

Error Message from Github Actions:

Using CPython 3.12.8 interpreter at: /opt/hostedtoolcache/Python/3.12.8/x64/bin/python3
Creating virtual environment at: .venv
error: Failed to generate package metadata for `*****`
  Caused by: Failed to resolve requirements from `build-system.requires`
  Caused by: No solution found when resolving: `hatchling`, `hatch-vcs`
  Caused by: Failed to fetch: `https://***-***.d.codeartifact.eu-west-1.amazonaws.com/pypi/***/simple/hatchling/`
  Caused by: error decoding response body
  Caused by: there are extra bytes after body has been decompressed
Error: Process completed with exit code 2.

Setup:
The code artifact url is setup in the pyproject toml

name = "aws-code"
url = "https://***-***.d.codeartifact.eu-west-1.amazonaws.com/pypi/***/simple/"

The credentials are setup as environment variables as documented here: https://docs.astral.sh/uv/guides/integration/alternative-indexes/#aws-codeartifact

@olafdeleeuw
Copy link

olafdeleeuw commented Dec 27, 2024

I can confirm same error occurs with Azure Artifacts. With v0.5.11 dependencies from our private Azure Artifacts library were installed by uv. Now, with v0.5.12 I get the same error as @okan-agca-entrix .

Creating virtual environment at: .venv
Resolved 128 packages in 1ms
  × Failed to build `emd-client @ file:///home/vsts/work/1/s`
  ├─▶ Failed to resolve requirements from `build-system.requires`
  ├─▶ No solution found when resolving: `hatchling`
  ├─▶ Failed to fetch:
  │   `[https://***.pkgs.visualstudio.com/***/_packaging/***/pypi/simple/hatchling/`](https://***.pkgs.visualstudio.com/***/_packaging/***/pypi/simple/hatchling/%60)
  ├─▶ error decoding response body

@kyriakost
Copy link

Can verify the error

@thiago-pythonic
Copy link

Error happens with Gitlab package registry:

Using Python 3.8.10 environment at: virtualenvs/***
error: Failed to fetch: `https://gitlab.com/api/v4/groups/***/-/packages/pypi/simple/***/`
  Caused by: error decoding response body
  Caused by: there are extra bytes after body has been decompressed

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

@olafdeleeuw
Copy link

No problem. Thanks!

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

@thiago-pythonic
Copy link

Thanks for the quick turnaround! 0.5.13 works just fine!

@olafdeleeuw
Copy link

Thanks! Also with Azure Artifacts. Everything works fine again with 0.5.13.

@flipdazed
Copy link

out of interest is there any way you can maintain previous versions in homebrew just in case there is a problem like this again? This caused us a bit of havoc because brew doesn't maintain any old versions

@charliermarsh
Copy link
Member

Hmm, I think that's ultimately up to Homebrew, since I didn't do anything specific to have it not publish to Homebrew. It's possible that the releases were just too close together, and so Homebrew never built and uploaded 0.5.12?

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

6 participants