Failing to upload to JFrog Artifactory v1.5.x
See original GitHub issue- I am on the latest Poetry version.
- I have searched the issues of this repo and believe that this is not a duplicate.
- If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).
- OS version and name:
System
Platform: darwin
OS: posix
Python: /Users/xxx/.pyenv/versions/3.7.4
- Poetry version:
Poetry
Version: 1.0.3
Python: 3.7.4
- Link of a Gist with the contents of your pyproject.toml file:
[tool.poetry]
name = "xxx"
version = "0.1.0"
description = ""
authors = ["XXX"]
[tool.poetry.dependencies]
python = "^3.7"
kfp = "^0.2.5"
[tool.poetry.dev-dependencies]
pytest = "^3.0"
pylama = "^7.7.1"
isort = "^4.3.21"
black = "19.3b0"
[tool.black]
line-length = 120
target-version = ['py37']
exclude = '''
(
/(
\.eggs # exclude a few common directories in the
| \.git # root of the project
| \.hg
| \.mypy_cache
| \.tox
| \.venv
| _build
| buck-out
| build
| dist
| venv
| docs
)/
)
'''
[tool.isort]
known_third_party = "pytest,kfp"
line_length = 120
lines_between_sections = 1
multi_line_output = 3
include_trailing_comma = true
skip="__pycache__"
[build-system]
requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"
Issue
When executing
poetry publish --build -r internal -u ${ARTIFACTORY_USER} -p ${ARTIFACTORY_PASS} -vvv
I got this:
Using virtualenv: /Users/xx/yy/venv
Building xxx (0.1.0)
- Building sdist
- Adding:
...
- Built xxx-0.1.0.tar.gz
- Building wheel
- Adding:
....
- Built xxx-0.1.0-py3-none-any.whl
Publishing xxx(0.1.0) to internal
- Uploading xxx-0.1.0.tar.gz 100%
[UploadError]
HTTP Error 500: Internal Server Error
Traceback (most recent call last):
File "/Users/yy/tools/poetry/1.0/lib/poetry/_vendor/py3.7/clikit/console_application.py", line 131, in run
status_code = command.handle(parsed_args, io)
File "/Users/yy/tools/poetry/1.0/lib/poetry/_vendor/py3.7/clikit/api/command/command.py", line 120, in handle
status_code = self._do_handle(args, io)
File "/Users/yy/tools/poetry/1.0/lib/poetry/_vendor/py3.7/clikit/api/command/command.py", line 171, in _do_handle
return getattr(handler, handler_method)(args, io, self)
File "/Users/yy/tools/poetry/1.0/lib/poetry/_vendor/py3.7/cleo/commands/command.py", line 92, in wrap_handle
return self.handle()
File "/Users/yy/tools/poetry/1.0/lib/poetry/console/commands/publish.py", line 81, in handle
client_cert,
File "/Users/yy/tools/poetry/1.0/lib/poetry/masonry/publishing/publisher.py", line 96, in publish
client_cert=resolved_client_cert,
File "/Users/yy/tools/poetry/1.0/lib/poetry/masonry/publishing/uploader.py", line 110, in upload
self._upload(session, url)
File "/Users/yy/tools/poetry/1.0/lib/poetry/masonry/publishing/uploader.py", line 205, in _upload
raise UploadError(e)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:8 (3 by maintainers)
Top Results From Across the Web
What should I do if an upload through the UI fails? - JFrog
1. Check if your current user has enough permission to deploy to this repository. 2. Check if this is failing over large files...
Read more >Known Issues - Artifactory 5.x - JFrog Wiki
Issue ID Affected From Version Fix Version
RTFACT‑15679 5.7.0 5.9.0
RTFACT‑14473 5.4.0 5.4.6
Read more >Known Issues - JFrog - JFrog Documentation
Importing a Release Bundle through the UI upload fails using airgap. Artifactory 7.38.10. Issue ID. Description.
Read more >How to resolve the issue when Artifactory fails to make secure ...
REASON: The error is caused because JVM that Artifactory runs on does not have root certificate of the remote URL trusted on its...
Read more >How to troubleshoot Docker problems - JFrog
The 401 HTTP code should be expected if Artifactory does not allow anonymous access to the repository in question. If a 200 OK...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok. I was able to work around this by removing ‘simple’ from the path per this post: https://github.com/python-poetry/poetry/issues/708
some app ‘bar’ notice the url does not have `/simple here’
then in a dependent project, I can add this library via poetry
notice that the url ends with
/simple
here//pyproject.toml
I’m getting the same error as well on Poetry 1.0.5. Trying to publish to Artifactory v5.3.0 rev 50045.
HTTP Error 500: Internal Server Error
I have no access to server side logs to provide.
EDIT: I printed out the Requests POST response in poetry/masonry/publishing/uploader.py and it provided the 500 error: No enum constant org.jfrog.repomd.pypi.model.PypiMetadata.MetadataVersion.v2_1
Older versions of Artifactory are affected by this issue, resolved in v6.1.0. https://www.jfrog.com/jira/browse/RTFACT-16189