Skip to content

Comments

Test foliage with curl retry backoff and download concurrency limit#1249

Closed
angerman wants to merge 2 commits intoIntersectMBO:mainfrom
angerman:test/foliage-retry-backoff
Closed

Test foliage with curl retry backoff and download concurrency limit#1249
angerman wants to merge 2 commits intoIntersectMBO:mainfrom
angerman:test/foliage-retry-backoff

Conversation

@angerman
Copy link
Contributor

Summary

Test PR to validate input-output-hk/foliage#115 which adds:

  • curl --retry 3 --retry-connrefused — retries transient HTTP errors (408, 429, 500, 502, 503, 504) with exponential backoff (1s, 2s, 4s)
  • Download concurrency cap at 20 via Shake Resource — prevents hundreds of simultaneous curl processes from overwhelming GitHub when running with -j 0

This addresses the repeated transient HTTP 502 failures seen in #1248 (failed 4 times before succeeding on the 5th manual re-run, each time on a different package).

Changes

  • Updated flake.lock to point foliage input at angerman/foliage@fix/retry-backoff-download-concurrency

Expected outcome

The CI build should succeed without the transient 502 failures that previously required manual re-runs.

Note: This is a test PR and should not be merged. Once validated, input-output-hk/foliage#115 should be merged upstream, and a separate PR should update foliage to the merged version.

Point foliage input at angerman/foliage#fix/retry-backoff-download-concurrency
(input-output-hk/foliage#115) to test the fix for transient HTTP 502
failures under high parallelism (-j 0).
The previous commit only updated flake.lock (locked section) but nix
resolves from the original URL in flake.nix, so the old foliage was
still being used. Update flake.nix to point directly at the PR branch.
@angerman
Copy link
Contributor Author

Reopening as a non-fork PR so CI has access to signing keys for deploy-check.

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