[Filesystem][FilesystemCommonTrait] Use a dedicated directory when there are no namespace #35290
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.
This PR fixes the following edge case:
/foo
and namespacea
: all files are written in/foo/a
(eg: it will write/foo/a/I/W/file
)/foo/a/I
directory (see [Cache] improve perf of pruning for fs-based adapters #33921 newscanHashDir()
method -a
is a possible dir value (seegetFile()
) so we look for it).The simple solution (suggested by @nicolas-grekas) is to put the "empty namespace" in a dedicated directory.
Bonus: that will fix the tests that currently always fail on AppVeyor. The file in the namespace
a
is a leftover from a previous test. Without this patch, I have the same fail on my Mac. I did not look why it currently passes on travis.