Repository navigation
fix(mount): request raw tar on github working-tree seed #537
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P2: This sends
gzip=0together withsourceArchive=1, a combination no code path in this repo exercises today.ExportGithubWorkingTreeTaronly emitsgzip=0when!seed.Gzip, and the existing contract testTestHTTPClientExportGithubWorkingTreeTarRequestsSourceArchive(internal/mountsync/http_client_test.go) asserts the opposite convention for source archives: a retained archive request carries nogzipparameter so the R2 object keeps its native gzip encoding. The comment claims the server ignoresgzipfor retained R2 archives, but that behavior ships in relayfile-cloud#312, which this PR says is still pending deployment. Against the currently deployed server, which has only ever seen source-archive requests without agzipparam (this call previously usedGzip: true), a large repo with a retained archive could be served the generated-tar path or a 413 — exactly the regression this flip is meant to cure. The local tar reader does adapt via Content-Type detection, so the risk is confined to server semantics, but the fix's correctness is unverified and untested: the raw-tar test usesGzip: falsewithSourceArchiveunset, so the shippedGzip: false, SourceArchive: truerequest shape is never covered. Confirm the server ignoresgzip=0whensourceArchive=1(once #312 deploys) and add a test asserting the combined request/response contract before relying on this path.Prompt for AI agents