-
Notifications
You must be signed in to change notification settings - Fork 955
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
502: Bad Gateway
on upload when Provides-Dist
metadata is invalid instead of error messages
#16452
Labels
Comments
rjdbcm
added
bug 🐛
requires triaging
maintainers need to do initial inspection of issue
labels
Aug 10, 2024
rjdbcm
changed the title
Received "502: Bad Gateway" on https://upload.pypi.org/legacy/
Aug 12, 2024
Provides-Dist
validation implementation differs from core metadata spec causing 502: Bad Gateway on upload.
I think we're parsing this correctly and the example in the spec is wrong, see my comment here. That said, I think returning a |
di
changed the title
Aug 12, 2024
Provides-Dist
validation implementation differs from core metadata spec causing 502: Bad Gateway on upload.502: Bad Gateway
on upload when Provides-Dist
metadata is invalid instead of error messages
di
removed
the
requires triaging
maintainers need to do initial inspection of issue
label
Aug 12, 2024
I've asked @DarkaMaul to take a look at this 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am getting bad gateway errors the past 14 hours, only from my GitHub actions runs. Wondering if this could be related to the cause of #9151 since everything else seems to be working. My local CI works with the same token on a different repo so
maybe this is some sort of regional proxy service outage or something.Edit 1: Now it is only for this repo but not for my other repos with the same GitHub workflow and token setup.
I have had the same result for GitHub actions runners 12,13, and 14.Does not seem to be related to which runner I use and seems to be isolated to this package repo.Edit 2: I have figured out the issue the core metadata specification for
Provides-Dist
shows a version format that will not work for warehouse as it usespackaging.requirements.Requirement
to validate this header. I have opened a PR over on the spec to change the example as well pypa/packaging.python.org#1586The text was updated successfully, but these errors were encountered: