fix(path): fix Windows path compatibility in recursively_copy_files#3319
Open
mramansayyad wants to merge 1 commit into
Open
fix(path): fix Windows path compatibility in recursively_copy_files#3319mramansayyad wants to merge 1 commit into
mramansayyad wants to merge 1 commit into
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
This PR fixes a Windows path compatibility bug in
recursively_copy_fileswhere the directory traverser fails to match skip paths containing Unix style separators (/) against Windows style separators (\).When copying files recursively on Windows,
os.walkyields paths with backslashes. Consequently,relative_file_pathconstructed viaos.path.joincontains backslashes (e.g.b\file2.txt), which fails to match againstskip_pathstypically provided with forward slashes (e.g.b/file2.txt).We normalize all intermediate relative paths to use forward slashes (
/), ensuring cross-platform correctness for all file and directory exclusion checks.Type of change
Checklist
CHANGELOG.mdunder the[Unreleased]section (or the relevantcheckpoint//export/changelog).