You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@di Thanks for the really fast follow-up. That would make sense. Do we have a guess at what the magic number would be to keep the worker from OOMing? If it's not too far off I can manually delete a few releases and try again.
I don't know of the "magic number" per se, but one thing we know if that the production runners have 2GM RAM each, and TestPyPI have 1GB RAM each.
This doesn't mean we won't hit the same problem in production, but it's a difference we can look at in reproducing the issue.
I tried to make a "generate me 2500 releases for a project" using the ReleaseFactory.create_batch() in a make shell, but ran into issues. Here's my start of that command if anyone wanted to try and complete it:
Note
This is likely only an issue with this specific project.
Describe the bug
I am unable to delete my project (
structlog-sentry-logger
) from test.pypi.org with the below 503 error:Expected behavior
For project deletion to succeed with old releases no longer associated with the project once it is recreated.
To Reproduce
Run through the "delete project" workflow on test.pypi.org for my project.
My Platform
Additional context
I hit my project size limits in September 2023 and wanted to delete the entire project to clear the 2400+ releases.
The text was updated successfully, but these errors were encountered: