4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	a825a4c904	The first read of a chain not laid out lays it out, so no read of the start is refused (issue 1121) ... The layout gate is switched on when the stores open (UseChainOpener), before attachTheChain; a read of the start came first, was refused, and the controller exited. A read that finds no marker now lays the builds out once, under a lock, and is refused only when that fails (a process without the lease).	2026-10-18 14:39:43 +02:00
jschoubben	7f074d9c94	A layout run again sets no pointer back and skips records already moved (issue 1121) ... The live start recorded its layout in chain_moved, so the marker is missing and the layout runs once more over the old keys. It wrote newest, worked, held, commit and source over the pointers of every build made since. Pointers are now made only where missing, and a record already under its new key is not read again.	2026-10-18 13:41:25 +02:00
jschoubben	e76ba966b3	Merge fix/1121-holds-released: delivery 2 on the builds' new layout (issue 1121) ... Delivery 2 deleted the move and chain_moved, so the layout of the builds under their modules is made by the controller's start (LayBuildsOut), recorded by the key layout.done in the builds bucket, retried every half minute with an urgent condition while it fails; the chain on the bus is refused until it exists. Its source readers use the module and pointer reads.	2026-10-18 13:39:24 +02:00
jschoubben	c795915315	Keep builds on the bus under their module, so no lookup reads the bucket whole (issue 1121, ADR 0427) ... Milestone 5 moved 8,599 build records onto the bus under bare build ids, each carrying its module's whole manifest. Every build lookup then read the whole bucket, and a delivery plan's send did that per module per machine while it held the plans and the machine's declaration: the send of build-agent never finished, and every other act and the status waited behind it. Builds now live under <module>.build.<id> (requests under req.<id>, id.<id> names a build's module), with pointer keys newest, worked, held, commit.<sha> and source.<reuse key> that move only to a newer build and are read as hints, repaired when wrong. Manifests are kept once in the same bucket under manifest.sha256-<hex>, so no grant the running bus lacks is needed. The old keys are laid out once at start, idempotently, and left unread. The calls a plan look makes on the silent clocks while it holds the plans are bounded, since the vendored kv.Keys ignores its context.	2026-10-18 13:32:31 +02:00