Skip to content

ci: retry downloads that a brief GitHub or registry failure would fail - #46

Merged
WilliamSmithEdward merged 1 commit into
mainfrom
ci/download-retry
Nov 17, 2026
Merged

WilliamSmithEdward merged 1 commit into
mainfrom
ci/download-retry

Conversation

@WilliamSmithEdward

Copy link
Copy Markdown
Owner

GitHub's download outage on 2026-11-09 returned 504s for over two hours,
and every scan job that fetched a pinned release with a single curl
failed. The release downloads here now pass --retry 3 --retry-all-errors,
so a short outage costs a retry instead of a failed check. The SHA-256
check that follows each download is unchanged. image_update.py is the
repo-standards copy (689522a), which retries its Docker Hub requests the
same way.

GitHub's download outage on 2026-11-09 returned 504s for over two hours,
and every scan job that fetched a pinned release with a single curl
failed. The release downloads here now pass --retry 3 --retry-all-errors,
so a short outage costs a retry instead of a failed check. The SHA-256
check that follows each download is unchanged. image_update.py is the
repo-standards copy (689522a), which retries its Docker Hub requests the
same way.
@WilliamSmithEdward
WilliamSmithEdward enabled auto-merge (squash) November 17, 2026 19:45
@WilliamSmithEdward
WilliamSmithEdward merged commit d9ffc5d into main Nov 17, 2026
21 checks passed
@WilliamSmithEdward
WilliamSmithEdward deleted the ci/download-retry branch November 17, 2026 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant