CODEWITHSUNDEEP
pythongoogle-cloud-platformhttp-errorpython-poetrygoogle-artifact-registry
Data minion
Data minion

Reputation: 49

Cannot publish Python artifact with Poetry to Google Artifact Registry because "HTTP Error 413: Request Entity Too Large"

I'm a quite new on Poetry usage. My need is just to push my Python library on my personal Google Artifact Registry. After launching those commands :

poetry config virtualenvs.create false
poetry config $repoName $urlOfTheRemoteArtifactRegistry
poetry config http-basic.$repoName $userName $userPwd
poetry publish -r $repoName --build

I have this stack error :

HTTP Error 413: Request Entity Too Large

  at /usr/local/Cellar/poetry/1.1.7/libexec/lib/python3.9/site-packages/poetry/publishing/uploader.py:216 in _upload
      212│                     self._register(session, url)
      213│                 except HTTPError as e:
      214│                     raise UploadError(e)
      215│ 
    → 216│             raise UploadError(e)
      217│ 
      218│     def _do_upload(
      219│         self, session, url, dry_run=False
      220│     ):  # type: (requests.Session, str, Optional[bool]) -> None

A 413 HTTP error means that my payload is to large, but in fact when i

du -h d 0

it, i've found only 100K. Is there a hidden option/hard-limit in poetry side ? Or it's in GCP ?

Any help/advise/thumbup would be appreciated.

Thank you in advance !

Upvotes: 5

Views: 4101

Answers (2)

BharathKumarRaju Dasararaju
BharathKumarRaju Dasararaju

Reputation: 117

This is fixed in the pre-release version of poetry 1.2.0a2

Here I have tested and it's working already for me. https://github.com/Bharathkumarraju/poetry-gcp-pypi

Upvotes: 2

Data minion
Data minion

Reputation: 49

[Update] I've solved the issue. It was related to the authentification and not to the size of the artifact. The 413 HTTP error led us astray about the actual root cause.

Upvotes: -1

Related Questions