-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Handle invalidation of corrupt cache files #2674
Comments
Could be part of the reason. However, I suspect that one is more to do with not being able to download the artifact (eg: html error page being downloaded). Fixing this will simply invalidate it and download again, which might again return the bad content. |
Also, clearing the cache doesn't remove these corrupted downloads |
I encountered the same issue and found this issue report. I worked around by manually downloading the tarball and putting it to the path shown in the error message. |
disabling the experimental new installer "fixes" this, but really just need to download to tmp, validate, and rename later instead of polluting the cache : |
using this fork, also fixes this for me: #3301 |
Solved in cc3f994 -- we now don't make a file available in the cache until the download is complete. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Issue
In cases where the a download fails, invalid or incomplete content downloaded, there seems to be a scenario where the cache file exists but was not cleaned up. Causing any following attempts to fail with an unpack error inside the pip subprocess. The below output is from an issue that happened when the underlying network changed during initial install and the process was killed. Then an install command was issued again, causing the issue.
The text was updated successfully, but these errors were encountered: