-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fs.stat or fs.lstat throws unknown error on some files (reparse point) #33024
Comments
Those are |
Adds support for IO_REPARSE_TAG_APPEXECLINK reparse points, used by Windows Store. Ref: nodejs/node#33024
Adds support for IO_REPARSE_TAG_APPEXECLINK reparse points, used by Windows Store. Ref: nodejs/node#33024
Adds support for IO_REPARSE_TAG_APPEXECLINK reparse points, used by Windows Store. Ref: nodejs/node#33024
Adds support for IO_REPARSE_TAG_APPEXECLINK reparse points, used by Windows Store. Ref: nodejs/node#33024 PR-URL: #2812 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Richard Lau <[email protected]>
A fix for this landed in libuv, it should make it way to Node rather soon. The stat calls will probably still not work though. Those links usualy point to the |
Fixed by #33446 |
This is not fixed. I can repro it with the latest release. |
What steps will reproduce the bug?
%USERPROFILE%\AppData\Local\Microsoft\WindowsApps
exists.fs.statSync("c:\\Users\\kanadig\\AppData\\Local\\Microsoft\\WindowsApps\\python.exe")
How often does it reproduce? Is there a required condition?
This repros 100%, make sure you are calling it on the files under
%USERPROFILE%\AppData\Local\Microsoft\WindowsApps\
with 0 size.What is the expected behavior?
Should not throw exception.
What do you see instead?
Additional information
See microsoft/vscode#95828
The text was updated successfully, but these errors were encountered: