-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
fs.writeFileSync
in Node 20 failed to write file in TMPDIR
#52079
Labels
fs
Issues and PRs related to the fs subsystem / file system.
Comments
atlowChemi
added
the
fs
Issues and PRs related to the fs subsystem / file system.
label
Mar 14, 2024
Works as expected with node-v20.7.0, failed with node-v20.8.0+. |
Change encoding Maybe #49884 related? Update: this works too.
to
|
fannheyward
added a commit
to neoclide/coc.nvim
that referenced
this issue
Mar 14, 2024
fannheyward
added a commit
to neoclide/coc.nvim
that referenced
this issue
Mar 14, 2024
fannheyward
added a commit
to neoclide/coc.nvim
that referenced
this issue
Mar 14, 2024
This looks similar to #50989 but #50990 should already be in Node.js 20.11.0. |
Seems to fail on Linux with Node.js 21.7.1 as well.
|
nodejs-github-bot
pushed a commit
that referenced
this issue
Mar 18, 2024
Fix a file permissions regression when `fs.readFileSync()` is called in append mode on a file that does not already exist introduced by the fast path for utf8 encoding. PR-URL: #52101 Fixes: #52079 Refs: #49691 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
rdw-msft
pushed a commit
to rdw-msft/node
that referenced
this issue
Mar 26, 2024
Fix a file permissions regression when `fs.readFileSync()` is called in append mode on a file that does not already exist introduced by the fast path for utf8 encoding. PR-URL: nodejs#52101 Fixes: nodejs#52079 Refs: nodejs#49691 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
marco-ippolito
pushed a commit
that referenced
this issue
May 2, 2024
Fix a file permissions regression when `fs.readFileSync()` is called in append mode on a file that does not already exist introduced by the fast path for utf8 encoding. PR-URL: #52101 Fixes: #52079 Refs: #49691 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
marco-ippolito
pushed a commit
that referenced
this issue
May 3, 2024
Fix a file permissions regression when `fs.readFileSync()` is called in append mode on a file that does not already exist introduced by the fast path for utf8 encoding. PR-URL: #52101 Fixes: #52079 Refs: #49691 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v20.11.1
Platform
macOS arm64
Subsystem
No response
What steps will reproduce the bug?
fs.writeFileSync
failed toEACCES: permission denied
error with Node 20, but works with Node 18.How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
Works with Node 18:
Additional information
No response
The text was updated successfully, but these errors were encountered: