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
adnan-kamili opened this issue
Sep 18, 2015
· 4 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.
Thanks, I think I understand what the issue is. See #1397 for background, it's the expected behavior insofar that it's not really possible to determine whether a folder is writable (without actually opening it) because that's controlled by the ACL, not the folder's metadata.
/cc @nodejs/platform-windows - Maybe it's a libuv issue, see also this comment.
Per #2949 (comment), I don't think a reliable fix is possible so I'll close this out. Trying to open the folder in write-only mode isn't reliable either, it misreports when the folder is locked.
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.
On Windows I have a shared folder with only Read permissions and the following code fails to detect that folder doesn't have write permissions:
I expect it to throw exception as per the docs.
The text was updated successfully, but these errors were encountered: