-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
Handling fs.constants.O_DIRECTORY flag #494
Closed
corwin-of-amber opened this issue
Jan 15, 2020
· 4 comments
· Fixed by #495, plastikfan/jaxom-ts#60 or plastikfan/zenobia-ts#38
Closed
Handling fs.constants.O_DIRECTORY flag #494
corwin-of-amber opened this issue
Jan 15, 2020
· 4 comments
· Fixed by #495, plastikfan/jaxom-ts#60 or plastikfan/zenobia-ts#38
Labels
Comments
The issue has been patched in this fork, although not completely. I will try to make a PR based on that. |
@corwin-of-amber thanks! |
corwin-of-amber
added a commit
to corwin-of-amber/memfs
that referenced
this issue
Jan 15, 2020
Extremely welcome 😄 |
streamich
pushed a commit
that referenced
this issue
Jan 15, 2020
## [3.0.4](v3.0.3...v3.0.4) (2020-01-15) ### Bug Fixes * 🐛 handle opening directories with O_DIRECTORY ([acdfac8](acdfac8)), closes [#494](#494)
🎉 This issue has been resolved in version 3.0.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
corwin-of-amber
added a commit
to corwin-of-amber/wasi-kernel
that referenced
this issue
Jan 15, 2020
Now contains O_DIRECTORY fix. (streamich/memfs#494)
This was referenced Mar 10, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Node.js, it is possible to open a directory with
fs.open
orfs.openSync
, specifying read access and optionally the flagfs.constants.O_DIRECTORY
.The effect of the flag is only that Node.js will raise
ENOTDIR
if the file is not a directory.In
memfs
, the flag is ignored when opening a file and rejected when attempting to open a directory (openLink
thinks the requested access is not read-only).The text was updated successfully, but these errors were encountered: