-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
fs.open differences on windows vs *nix #3643
Copy link
Copy link
Closed
Labels
docIssues and PRs related to the documentations.Issues and PRs related to the documentations.fsIssues and PRs related to the fs subsystem / file system.Issues and PRs related to the fs subsystem / file system.libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.
Metadata
Metadata
Assignees
Labels
docIssues and PRs related to the documentations.Issues and PRs related to the documentations.fsIssues and PRs related to the fs subsystem / file system.Issues and PRs related to the fs subsystem / file system.libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.
If you create a directory, and then try to use
fs.opento open it, you get differing behavior on windows and *nix if the flags area+.Example:
After looking through the libuv code, it looks like https://github.com/libuv/libuv/blob/v1.x/src/win/fs.c#L479-L480 is responsible for this. Is this intended or should this operation show the same behavior on all platforms?