Skip to content

release: retry transient upstream errors when fetching release inputs - #360

Merged
andersalm merged 1 commit into
developfrom
fix/upstream-fetch-retry
Oct 14, 2026
Merged

andersalm merged 1 commit into
developfrom
fix/upstream-fetch-retry

Conversation

@andersalm

@andersalm andersalm commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

The alpha.15 package rebuild lost its 60-minute Mac job to one HTTP 504 from an upstream host (run 38241639459, attempt 1). Opening an upstream source now retries 429/5xx, timeouts and dropped connections three more times, 2, 4 and 8 seconds apart; redirect policy, size bounds and permanent errors are unchanged. A test proves two 504s then success pass, four 504s fail, and a 404 is not retried. CI precheck PASS before push.

Part of #89.

The alpha.15 package rebuild failed its 60-minute Mac job on one HTTP 504
from an upstream host. Opening an upstream source now retries 429/5xx,
timeouts and dropped connections three more times, 2, 4 and 8 seconds apart;
redirect policy, size bounds and permanent errors are unchanged.
@andersalm
andersalm merged commit 4a91040 into develop Oct 14, 2026
15 checks passed
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