lukechilds/node - node - Gitea: Git with a cup of tea

Tree: 9777890f5d

Ben Noordhuis b011811a9f fs: fix fs.truncate() file content zeroing bug fs.truncate() and its synchronous sibling are implemented in terms of open() + ftruncate(). Unfortunately, it opened the target file with mode 'w' a.k.a. 'write-only and create or truncate at open'. The subsequent call to ftruncate() then moved the end-of-file pointer from zero to the requested offset with the net result of a file that's neatly truncated at the right offset and filled with zero bytes only. This bug was introduced in commit `168a5557` but in fairness, before that commit fs.truncate() worked like fs.ftruncate() so it seems we've never had a working fs.truncate() until now. Fixes #6233.		11 years ago
..
addons	test: modify async native test.js to test for #4820	12 years ago
disabled	Merge remote-tracking branch 'ry/v0.8' into master	12 years ago
fixtures	debugger: breakpoints in scripts not loaded yet	12 years ago
gc	test: use the debug build of node-weak when necessary	13 years ago
internet	test: move two tests from simple/ to internet/	12 years ago
message	process: separate nextTick domain logic	12 years ago
pummel	test: fix pummel/test-net-connect-memleak	12 years ago
simple	fs: fix fs.truncate() file content zeroing bug	11 years ago
common.js	test: optionally set common.PORT via env variable	12 years ago