Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use string lengths instead of regexp to extract path #33704

Merged
merged 1 commit into from
Aug 23, 2018

Conversation

matthewd
Copy link
Member

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. πŸ•°πŸ•΅πŸ»β€β™‚οΈ

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant