Use string lengths instead of regexp to extract path #33704
Merged
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.
The regexp was introduced in 186ac4c, and looks cosmetic. While they should be functionally identical in theory, in practice, case insensitive (but preserving) filesystems can give results that are differently-cased from the pattern we supplied.
I don't know how to force the filesystem to do the surprising thing, even when running in an environment that could, so no new test.
Fixes #18660.
I'd held off on making this change for a Very Long Time, because I mistakenly thought the use of the regexp was important for safety (and introduced more recently). It turns out that was wrong, and I just needed to dig into history to better understand how we got here. π°π΅π»ββοΈ