Artifact 55c1b0c6b5db779cf030afd2c2ed5d465b7701906a0e84081210c0f406dba89d:
- File
internal/index/supersede_test.go
-
2026-08-26 12:53:49
— part of check-in
[c2930a1351]
on branch landings-batch
— One open landing per branch: refuse the second, and agree which wins
zit#127 left this as 'probably yes, refused by name on the second' and neither side enforced it, so two threads naming one branch produced two open landings with nothing saying which accept should honour.
Both halves, because refusing is not enough: two peers can each open one in separate clones and both are valid artifacts when they meet. landing.open refuses by name; the fold picks the newest root as current and marks the rest, recomputed each fold so a record revives if the one that displaced it is settled.
Settled landings never take part — a later proposal for the same branch is a new proposal, not a correction of a finished one. Nothing is deleted; a record somebody argued in is not noise. (user: dmestas, size: 4786) [annotate] [blame] [check-ins using]
- 2026-08-26 12:58:43 — part of check-in [db0ed60824] on branch trunk — Accepted. Ordering by the DAG, one current landing per branch, and a verdict that was already an artifact. (user: dmestas, size: 4786) [annotate] [blame] [check-ins using]
-
2026-08-26 12:53:49
— part of check-in
[c2930a1351]
on branch landings-batch
— One open landing per branch: refuse the second, and agree which wins