package-analysis
package-analysis copied to clipboard
Race condition between when a new PyPI package is detected and when the package is installable
trafficstars
Roughly 20-40% of errors occur due to PyPI package updates being detected and scheduled prior to the package itself being ready to install.
This causes many package updates to be missed.
The race condition is likely a result of PyPI publishing the package update prior to the files being available over the CDN.
The plan to solve this issue is to reorient the project towards analysing "artefacts" instead of "package-version".
For most ecosystems "artifact" == "package-version", however this is not the case of ecosystems like PyPI (as per description), or even Composer/Packagist (where "package-version" == "repo tag" - yuck).