One of my colleagues has spotted some odd behaviour with the List Files/Folders node when using a windows based network share.
Example path: \data\myfoldershare\sub folder\
The List Files/Folders node find 12 files in this folder but should find 79.
If I run a Java snippet with a simple File#listFiles() call then all 79 files are found, so our initial thought of it being a network/VPN glitch doesn’t look right.
If we copy the files locally the List Files/Folders node finds them all.
If there’s something I can do to provider a more useful bug report let me know, not sure how to provide you a reproducible example in this scenario. But if you tell me what class to look in I’m happy to step through the code.
From further investigation the files filtered out have the ReparsePoint attribute. I don’t know why some files have this attribute but presumably it’s something to do with the underlying filesystem on our network share.
I think my conclusion is we’d like to have an option in the node to allow files that return true to isOther() to pass the filter and be listed. Maybe extending this so also optionally include symbolic links?
This is available in the nightly build and it would be great if you could try it and let us know if it fixes your problem. If no problems come up with this new option it will be released with the 4.3.3 release.