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
There is a workflow that tries to upload the package to TestPyPI, and it started failing with:
WARNING Error during upload. Retry with the --verbose option for more details.
ERROR HTTPError: 400 Bad Request from https://test.pypi.org/legacy/
Project size too large. Limit for project 'pytsql' total size is 10 GB.
See https://test.pypi.org/help/#project-size-limit
This should not be critical.
We could consider:
Deleting what's already there to free up all space and deal with this when it happens again
Disable the workflow that uploads to testpypi
The text was updated successfully, but these errors were encountered:
I don't think it makes sense to upload to TestPyPI for every branch. Also, since I don't think anyone is actually making sure that whatever is pushed to TestPyPI is actually installable and working, it has no compelling purpose.
Maybe it'd make sense for tags that are meant to be released but then pushing to PyPI upon tag wouldn't make much sense.
My take, is just to remove the publish to TestPyPI altogether.
There is a workflow that tries to upload the package to TestPyPI, and it started failing with:
This should not be critical.
We could consider:
The text was updated successfully, but these errors were encountered: