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
TylerLeonhardt opened this issue
Jan 4, 2021
· 3 comments
Labels
fsIssues and PRs related to the fs subsystem / file system.libuvIssues and PRs related to the libuv dependency or the uv binding.windowsIssues and PRs related to the Windows platform.
This only seems to happen with AppExecLink reparse points on Windows. Regular SymbolicLinks are fine on Windows and give the expected behavior.
Also, fs.lstatSync works with these AppExecLink's which I'm guessing is because lstat operates on the symlnk and not the file that the symlnk points to.
The text was updated successfully, but these errors were encountered:
TylerLeonhardt
changed the title
fs APIs don't really understand AppExecLink reparse points on Windowsfs APIs don't understand AppExecLink reparse points on Windows
Jan 4, 2021
The fs.readlinkSync workaround is likely just giving you the details of the SystemUDPLauncher.exe and not the pwsh.exe file here. Hmm... definitely thinking this is something that needs to be fixed at the libuv level.
/cc @nodejs/libuv
jasnell
added
the
libuv
Issues and PRs related to the libuv dependency or the uv binding.
label
Mar 5, 2021
fsIssues and PRs related to the fs subsystem / file system.libuvIssues and PRs related to the libuv dependency or the uv binding.windowsIssues and PRs related to the Windows platform.
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
100% repro rate
What is the expected behavior?
What do you see instead?
Additional information
This only seems to happen with AppExecLink reparse points on Windows. Regular SymbolicLinks are fine on Windows and give the expected behavior.
Also,
fs.lstatSync
works with these AppExecLink's which I'm guessing is because lstat operates on the symlnk and not the file that the symlnk points to.Related issues:
#33024
microsoft/vscode#95828
The text was updated successfully, but these errors were encountered: