Fix: use binary content type for file source uploads#10
Closed
Fix: use binary content type for file source uploads#10
Conversation
uploadSingleFile was auto-detecting content type from the file extension, causing .tgz files to be marked as tgz. Rage then extracts tgz objects as archives instead of placing them as single files, breaking npm install from the tarball at mount time. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
uploadSingleFilewas auto-detecting content type from file extension —.tgzfiles were tagged astgz, causing rage to extract them as archives instead of placing them as single filesbinarycontent type for file uploads so the file is placed as-is on the devboxdetermineContentTypeso it remains available for future useContext
This broke
source-type: filefor npm package tarballs — the tarball was extracted instead of being kept whole fornpm install -g ./file.tgzat mount time.Test plan
.tgzfile and verify it's placed as a single file (not extracted)npm install -g ./agent.tgzworks in setup commands🤖 Generated with Claude Code