Error: UNKNOWN: unknown error, lstat on WSL symbolic links

Thanks for your effort on this project. I’m using fast-glob in a PHP language server and am getting reports from users about lstat errors. Most of these users are on Windows and are using WSL, though a minority appear not to be using WSL.

This is the issue containing most of the information: https://github.com/bmewburn/vscode-intelephense/issues/260

This may also be useful: https://github.com/Microsoft/WSL/issues/1524

I’m not a Windows user myself but will try and add some further info later.

Environment

Windows

Actual behavior

Error: UNKNOWN: unknown error, lstat 'e:\firma\fbpopular\public\storage'

Expected behavior

No error.

Steps to reproduce

1. Try and find files in a dir structure that contains symbolic links on windows WSL

[mrmlnc]

So, after research: the node-glob package just ignore error from lstat call.

This is will be work correctly after #163, but only with Node.js 10.10+. I’ll think about how to handle situation on Node.js below 10.10.

[mrmlnc]

Unfortunately, the correct behavior is only guaranteed for Node.js 10.10+. For the correct operation of the package requires information about what the file in front of us: symbolic link, file or something else. We cannot ignore the lstat error, otherwise, there will be inconsistency between modes: string, dirent and stat.

So, right now VS Code build with Node.js 10.2.0. The next update was delayed (https://github.com/microsoft/vscode/issues/61787).

I will describe this behavior in the documentation.