fs.accessSync not working properly on Windows

[adnan-kamili]

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:

fs.accessSync("\\\\machine1\\shared",fs.W_OK);

I expect it to throw exception as per the docs.

[bnoordhuis]

What does fs.statSync() print for that folder?

[adnan-kamili]

Following is the output of fs.statSync()

{ 
  dev: -1710066481,
  mode: 16822,
  nlink: 1,
  uid: 0,
  gid: 0,
  rdev: 0,
  blksize: undefined,
  ino: 562949953426603,
  size: 0,
  blocks: undefined,
  atime: Fri Sep 18 2015 16:13:15 GMT+0530 (India Standard Time),
  mtime: Fri Sep 18 2015 16:13:15 GMT+0530 (India Standard Time),
  ctime: Fri Sep 18 2015 16:13:15 GMT+0530 (India Standard Time),
  birthtime: Fri Sep 18 2015 15:46:37 GMT+0530 (India Standard Time) 
}

[bnoordhuis]

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.

[bnoordhuis]

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.