fix: keep temporary copies on their volume - #434
Merged
Conversation
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.
Description
Large worktree and app copies on another volume can silently materialize in system temp and exhaust the internal disk. Staging stays outside Git working trees to preserve secret-file protection.
Solution
Select private, writable staging on the operation's volume for warming, app preparation, release swaps, and fingerprint checks.
STIM_TMPDIRor machinetempDircan override placement. Doctor reports when that override or the build-cache layout requires full cross-volume copies. Failed swaps remove their staging directories.Test plan
Fixes #431.