Repository navigation
Conversation
This was added to investigate composer#11148, which turned out to be GitHub serving truncated zipballs. Those are now detected and retried at download time, so the extra output and response header collection are no longer needed.
Seldaek
force-pushed
the
remove-zip-debug-output
branch
from
October 1, 2026 09:27
e05fa1b to
dfba1da
Compare
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.
Follow-up to #13094, to be merged later, once that has been out for a while and the reports in #11148 have stopped.
#11148 was GitHub occasionally serving truncated zipballs. #13094 now detects these at download time and retries them. This PR removes what was added to investigate that issue:
unzipfails on GitHub ActionsFileDownloader::$responseHeaderscollection that fed it (@internal)