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
According to pypi/warehouse#12214 , it has been a long-existing problem for the PyPI CDN to serve stale JSON API response, causing persisting error in syncing. This time, the mirror has been broken for over a week.
Could we implement a workaround in bandersnatch, allowing setting aside the problematic package, and continue to sync other packages? That's to say, to force fetch the change log even though the todo file exists?
The text was updated successfully, but these errors were encountered:
Howdy - Sure has been a long standing issue. #1335 removed our PURGE call that use to assist / workaround this. But as you can see, we have not been able to workaround it.
Could we implement a workaround in bandersnatch, allowing setting aside the problematic package, and continue to sync other packages? That's to say, to force fetch the change log even though the todo file exists?
How do you want to detect the problematic package? From there how should we store problematic package state?
The current workaround is to just rm the TODO file.
According to pypi/warehouse#12214 , it has been a long-existing problem for the PyPI CDN to serve stale JSON API response, causing persisting error in syncing. This time, the mirror has been broken for over a week.
Could we implement a workaround in bandersnatch, allowing setting aside the problematic package, and continue to sync other packages? That's to say, to force fetch the change log even though the
todo
file exists?The text was updated successfully, but these errors were encountered: