Fix Windows path detection in cleanPathWithBase #644
+5
−1
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
Fix
cleanPathWithBaseto usefilepath.IsAbson the original path before converting to forward slashes. This correctly handles Windows paths likeC:\foowhichfilepath.IsAbsrecognizes butpath.IsAbs(afterToSlashconversion toC:/foo) does not.Problem
When using
WithStartDirectoryon Windows, absolute paths likeC:\Users\fooare incorrectly treated as relative paths because:filepath.ToSlash(filepath.Clean("C:\\Users\\foo"))→C:/Users/foopath.IsAbs("C:/Users/foo")→false(only checks for/prefix)Solution
Check
filepath.IsAbs(p)on the original path before theToSlashconversion.filepath.IsAbsis platform-aware and correctly identifies Windows absolute paths.Related
This fix resolves Windows SFTP path handling issues in owenthereal/upterm#440