fix: handle empty/windows paths correctly in base-path-aware path fixer #984
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.
there are a couple issues in the base-path-aware path fixer:
empty paths are not skipped
""
./
for windows paths due to the other bug fixed in this PR)""
, so it does not early-exit./
so the path is turned into""
os.path.relpath()
gets madincorrect usage of
PurePath
the base-path-aware path fixer uses the parent directory of the coverage file as its base. we use
PurePath
to figure out that parent directory, as it does not perform any actual disk operations, it's just path manipulations.the issue is,
PurePath
on our Linux prod servers will instantiate aPurePosixPath
, even if the path we are using is clearly a windows path likeC:\Users\matt
. this is wrong:the fix is to use
PureWindowsPath
for windows paths andPurePosixPath
otherwiseLegal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.