fix: disable gc.auto after blobless clones to prevent race condition#6
Merged
critesjosh merged 1 commit intomainfrom Mar 2, 2026
Merged
fix: disable gc.auto after blobless clones to prevent race condition#6critesjosh merged 1 commit intomainfrom
critesjosh merged 1 commit intomainfrom
Conversation
Blobless clones with sparsePathOverrides trigger on-demand blob fetches, each of which runs `git gc --auto`. Concurrent gc processes collide with "unable to write new index file" errors. Setting gc.auto=0 right after clone prevents this. Safe for read-only clones used only for code search. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
🎉 This PR is included in version 1.9.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
git config gc.auto 0immediately after each--filter=blob:noneclone incloneRepo()git gc --autoprocesses from colliding during on-demand blob fetches triggered bysparsePathOverridescheckoutsaztec-packages(which usessparsePathOverridesto pull docs from thenextbranch)Context
Blobless clones (
--filter=blob:none) fetch blobs on demand. WhensparsePathOverrideschecks out files from a different branch (e.g.,origin/next), each blob fetch triggersgit gc --auto. Multiple concurrent gc processes race to write the same index file, causing failures.Setting
gc.auto=0is safe here because these are read-only clones used only for code search — they never accumulate loose objects over time.Test plan
gc.autoconfig call~/.aztec-mcp/repos/aztec-packagesand re-sync to verify clone succeeds without gc errors🤖 Generated with Claude Code