NEC-345: A tool's write meeting a remote change not yet written keeps a copy the Markdown hardness checker calls unexplained #322
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!322
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-345-a-tools-write-meeting-a-remote-change-no"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task: NEC-345 — https://projectron.nerchure.com/tasks/366
A note's pending write, meeting a file another tool had edited while the document had moved too, kept the file in .nectenda-backups before merging it whatever the merge would do. The copy is of the file and can only save a line the file held; when every line of the file and of the document survives the merge it holds nothing the note does not, and Obsidian's modify event for the same write already merged such a file with no copy, so the copy came down to a few-millisecond race (Markdown hardness seed 1209056253, round 82). SAFE-A30's exception now also covers a merge that only adds, decided by a dry run on the merged text (mergeMayLose) at both SAFE-A30 sites; a refused line merge or any lost line keeps the file as before. The copy's log line no longer says the note was not being synced. Tests seen failing first and the helper mutation-checked both ways; a fresh-context review found no bug; the seed replayed for 25 minutes passes round 82 and ends clean; gate-local green at
fd86ced5.Spec:
docs/changes/NEC-345-copy-only-when-the-merge-may-lose/spec.mdChangelog
A note changed by another tool while a collaborator's edit was still waiting to be written no longer leaves a copy in .nectenda-backups when the merge keeps every line of both.