-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
openSync/writeSync/closeSync produces empty file #7879
Comments
The |
|
Sounds like you've run into the same problem for |
@papandreou: looks alike. Will the fix there also fix my issue? |
I don't think it will in its current state, no. I'm on holiday for the next week, but will make sure to pick it up if noone else has landed a fix in the mean time. It's weird, seems like this bug has been there since at least 0.6. It really is the most basic form of |
@papandreou, alternatevly you could change this here Line 1001 in c86c1ee
WriteBuffer accepts the following spec:
As I understand |
Fixed by #7856 (released in 7.2.0). This issue can be closed now. |
Code:
produces empty file. Expected is that it writes whole buffer. Note that
fs.writeSync(fd, "Was here.\n");
writes whole string.v6.2.2
Darwin MacBook-Pro-3.local 14.5.0 Darwin Kernel Version 14.5.0: Thu Apr 21 20:40:54 PDT 2016; root:xnu-2782.50.3~1/RELEASE_X86_64 x86_64
fs(?)
The text was updated successfully, but these errors were encountered: