4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	275ddd76e8	Keep rollouts and the merges they answer in the rollouts bucket (issue 1092) ... Once chain_moved records the kind, a plan is a key of the rollouts bucket under its id and the open batch is the same key in state assembling. A save refuses a copy another save moved since (the plan's own Revision, kept in its value, counts saves) and keeps the merges the record holds, so a copy read before a merge moved cannot lay it back. The merges a batch or walk answers are the record's held field, with the columns the table had; a merge no plan answers stays, flagged, in the record that held it last, or in the record kept for those. A merge moved to a plan is written to the receiving record first and then taken from the giving one; one found in both is read from the one it entered last and repaired at the next cut. Plans and merges are read from a view kept by one watch of the bucket. A bus that does not answer, a lease lost and a key moved are now not-now like the store being away, so a merge whose plan could not be written is held and handed over again, never acknowledged. The start moves release_plan and batched_merge into the bucket, one kind, counted against both tables.	2026-10-18 03:06:50 +02:00
jochen	065cfa0d1d	Owe a merge to the record from its branch's first kept merge (hq ADR 0276 review)	2026-10-10 13:54:40 +02:00
jochen	0e0e143055	Keep a merge a cut made history, and build a batch's walk at the branch (hq ADR 0276 review)	2026-10-10 13:48:31 +02:00
jochen	96fc4209d3	Assemble merges in a rolling window and walk each batch once (hq ADR 0276, issue 362) ... Every merge opened a walk and the next merge of the branch superseded it: two catalogue merges 18 s apart left a walk no delivery held, and the operator started it by hand 58 minutes later. A merge now joins the open batch, kept in the store (migration 0089), which is cut into one walk when no merge came for merge-window (90 s) or at merge-window-at-most (10 min): one commit per repository, the latest of its branch, with every file the batch's merges changed. One walk at a time; a started walk is never superseded, a waiting one is folded into the next. The walk names every merge it answers on the wire (delivery.merges, taken_over_by, batch). A failed walk walks its earlier merges alone, newest first, until one is delivered. A delivery group's order becomes tier edges inside the walk. plans shows the batch assembling; S18 and S19 bound its waits; S16 names the merges a waiting walk answers.	2026-10-10 13:20:04 +02:00