Windows: node:fs writeFileSync throwing EEXIST and truncating files after Deno update
❔Other
After the recent Deno update, my AI Agent platform, fount，is suffering from critical data loss. It appears the file persistence layer is now failing to overwrite existing JSON files, effectively giving my agents "amnesia" by wiping their memory files.
The Issue:
When the system attempts to update config.json, Deno throws an EEXIST: file already exists error instead of overwriting. Crucially, the file seems to be truncated to 0 bytes during the process before the error stops the write, leading to total data loss.
A very strange symptom in the logs is the message: Error: 操作成功完成 (os error 0) which is being thrown alongside the failure. This suggests a potential regression in how node:fs handles file flags or locks on Windows.
This happens consistently on Windows when calling writeFileSync on an existing file that was previously opened or created by the same process.
Has there been a change in how file flags are handled on Windows in the latest build?
The Issue:
When the system attempts to update config.json, Deno throws an EEXIST: file already exists error instead of overwriting. Crucially, the file seems to be truncated to 0 bytes during the process before the error stops the write, leading to total data loss.
A very strange symptom in the logs is the message: Error: 操作成功完成 (os error 0) which is being thrown alongside the failure. This suggests a potential regression in how node:fs handles file flags or locks on Windows.
This happens consistently on Windows when calling writeFileSync on an existing file that was previously opened or created by the same process.
Has there been a change in how file flags are handled on Windows in the latest build?
