Fix pod install issue when git's core.fsmonitor feature is enabled (again)
#12349
Conversation
This file contains 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
justinseanmartin
force-pushed
the
jmartin/12158-redux
branch
from
595655d
to
75d5503
Compare
dnkoutso
approved these changes
Apr 16, 2024
justinseanmartin
force-pushed
the
jmartin/12158-redux
branch
from
75d5503
to
bc5fdc6
Compare
paulb777
approved these changes
Apr 16, 2024
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.
Use rsync to exclude copying the
fsmonitor--daemon.ipc(or anything under the.gitdirectory for that matter). From the original PR #12158:I don't think this change was causing any of the issues that led to the revert in #12229 for the 1.15.2 release. I verified that I can reproduce the issue in #12226 against 1.15.0 and it does not reproduce against this branch.
This should again resolve #11640.