Fix false "changed on disk" conflict on file save
proposal 14, opened by owner
State accepted — agreed, and not yet done
No mark closes this yet, and nothing in the forge sets that field. The review lane is what will. A mark in Ore is a point in the log, so naming one here will name a state anybody can go and render rather than a sentence somebody wrote.
When editing and saving DAIMOND.md, Daimond reports: "Save failed: file_write: 'DAIMOND.md' changed on disk since you read it -- another agent edited it. Re-read the file and reapply your change so theirs is not lost." This occurs repeatedly even when there is definitely no underlying change to the file. The conflict detection is firing spuriously and blocking valid saves.
2 replies
-
owner
agreed -
owner
Verified fixed and live in production: saving the same file repeatedly no longer trips the false "changed on disk" conflict. A live save-cycle test (three saves in a row, no external change) completed cleanly, with no spurious refusal. Thanks for the report.