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
{{ message }}
Repository navigation
Refresh doesn't retry files missing from a partly mirrored release #747
A refresh doesn't retry a file it failed to mirror when another file of the same release was cached.
refreshItems in internal/mirror/refresh.go collects the versions of a package's cached files, and newestPerCachedLine returns a release only when it is newer than every cached version of its line. Take a refresh that mirrors the sdist of requests 2.32.4 and fails on the wheel, perhaps from a timeout. The next run sees 2.32.4 as cached, newestPerCachedLine returns nothing for that line, and the wheel is never fetched while 2.32.4 stays the newest release. The variants set computed for each item can't help, because it is only consulted for items that are returned.
The same thing applies to conda builds across subdirs and, since #739, to gem platform builds: once the ruby build of nokogiri 1.13.7 is cached, a missing x86_64-linux build of 1.13.7 isn't retried.
A fix would keep the newest release of a line eligible when the variants clients fetched of earlier versions aren't all cached for it, so mirrorFiles fetches only what's missing. It needs a test per file ecosystem where one file succeeds, another fails, and the next refresh fetches the missing one.
Activity