git.latest with force_clone fails when it can't create a target directory that already exists #40524
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.
What does this PR do?
Fixes the
force_clone
option ingit.latest
state, by removing the target directory's contents, instead of target directory. Previous behavior runs into a corner case where target directory can't be recreated due to user's lacking priviledges to write in target's parent dir.What issues does this PR fix or reference?
#31363
Reference SLS
Previous Behavior
New Behavior
Tests written?
No
Given how the issue remained untouched for over a year, I wouldn't expect the fix to be trivial, so I'm welcoming any feedback related to this issue.