Repository navigation
ci: retry dependency clones with HTTP/1.1 and verbose transfer log - #182
Merged
Merged
Conversation
The partial-clone change (#181) did not resolve the intermittent 'Failed sending HTTP request' errors when cloning SwagCommercial: the failures occur within ~60ms, before any pack data is transferred, so transfer volume was not the bottleneck. curl error 55 at that stage is a typical symptom of an HTTP/2 stream reset while the request body is being sent. SwagCommercial's fetch negotiation request is ~15x larger than that of other dependencies (3707 refs vs ~250), which matches it being the only repo affected. None of the involved actions changed when the failures started (2026-07-18), pointing at a runner-image or transport-level change. Retry attempts now force http.version=HTTP/1.1 and enable GIT_CURL_VERBOSE (auth headers are redacted by git). If retries succeed consistently while first attempts keep failing, HTTP/2 is confirmed as the trigger and can be disabled for the first attempt as well; if they keep failing, the verbose log shows where the connection breaks.
Florian Ruppel (fruppel)
requested review from
Malte Janz (MalteJanz) and
Nicolas Fortier (nfortier-shopware)
July 20, 2026 11:19
Nicolas Fortier (nfortier-shopware)
approved these changes
Jul 20, 2026
Florian Ruppel (fruppel)
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Follow-up to #181, which did not resolve the intermittent
Failed sending HTTP requesterrors when cloning SwagCommercial (e.g. this run).What we know now
setup-extensionunchanged since 06-11,setup-shopwaresince 06-08 → points at a runner-image or transport-level change (runners now ship git 2.54.0).Change
Retry attempts (2 and 3) now:
http.version=HTTP/1.1GIT_CURL_VERBOSE(git redacts auth headers in these traces)First attempts stay on the default transport, so the logs become a live experiment: