You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's my understanding that in C the function pointer to find_files_with_pattern may be left unset. However the rust wrapper implements its default implementation here.
Problem is this: The C code uses find_fileshere to get the content of the directory. Then it gets here, then here, then here and finally ends up in MatchFiles.
It's my understanding that in C the function pointer to
find_files_with_pattern
may be left unset. However the rust wrapper implements its default implementation here.Problem is this: The C code uses
find_files
here to get the content of the directory. Then it gets here, then here, then here and finally ends up inMatchFiles
.In
MatchFiles
it checks whetherFindFilesWithPattern
is set, which it is and thuspatternCheck
is NOT set toTRUE
.Because of that this condition always passes on the first entry that
find_files
returns.This bug can be reproduced with your memfs example:
The text was updated successfully, but these errors were encountered: