dont use false
as cache key for non utf8 path in normalizePath
#22520
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.
since
json_encode
returnsfalse
if it's input isn't utf8, all non utf8 paths passed to normalizePath will currently return the same cached result.Fixing this makes working with non utf8 storages a little bit more possible for apps
Signed-off-by: Robin Appelman robin@icewind.nl