From 2e7269f1a1b80fef6b7a332cd437f374431d8bad Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 01:04:56 +0100 Subject: [PATCH] Design 47 H: section 10, finding 95 --- .../01-to-be/47-milestones/H-deliver-the-delivery-system.md | 1 + 1 file changed, 1 insertion(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md index 0fd38830..9da8d7d0 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md +++ b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md @@ -611,3 +611,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | Beyond the publish re-pin, three more whole recomputes of the indexer (on a build module's assignments change, on a toolchain report, and by the recompute tool) moved fingerprints with no kept revision, and the assigner (`mesh-delivery-assigner`) derived a pipeline's source from its key, which now carries the revision number; the indexer (`mesh-delivery-indexer`), the pipeline runner and the assigner. Settled by H-A-217 (any recompute that moves a fingerprint keeps a revision of `call-kind` recompute naming its reason; the runner treats every revision whose kind is not take-in alike, one pipeline for its movers) and H-A-216 (the assigner keeps the source the pipeline's end names and sends it in pipeline-wanted beside the revision). In build by the pin kind's second owner (row 91). | settled in H1 once delivered | | The joined pipeline runner (`mesh-delivery-pipeline`) crashed at every start on the control-node ("concurrent map writes" in its per-mover step store: the store's shared maps were written under each pipeline's lock only, while the start placed several branches' waiting pipelines at once) and was rolled back within a minute. Before dying it had split two kept pipelines into per-mover keys, and the old runner then placed one running pipeline's steps again from the emptied record, losing that record's history; no hand repair, as the new runner composes from the keys; the pipeline runner. Settled in H1 by a mutex over the store's maps and a run of the race detector over the runner's start path with kept pipelines. Owed: every module's unit and integration suites run under the race detector in the check, and a tool that lists the runner's state keys (a whole list exceeds the bus; no key listing exists). | H1 (the fix); H2 (the check and the tool) | | The indexer (`mesh-delivery-indexer`) refused its own take-in-again tool's ask ("a takeins value naming no hand act the indexer serves"): the decoder of a take-in ask kept a hand-written list of hand-act fields that the new field was not added to, and no test sent a tool's value through the decoder; the indexer. Settled in H1 by deriving the check from the ask's fields, and by a table test that decodes every tool's value. Owed: the same table test for every module whose tools write asks its daemon decodes. | H1 (the fix); H2 (the kind across modules) | +| The seat mesh-catalog's revision verb answered from the tools bundle's view of the trunk in memory, which ran one or more revisions behind the kept revisions once releases kept several in a row, so the pipeline runner waited minutes for a revision the indexer had kept (four minutes for revision 52) and the builder's picture failed a pipeline's first builds past its bound (rows 68 and 84); the indexer (`mesh-delivery-indexer`) and the builder. Settled by H-A-222 (the verb answers the newest kept revision read from the store at the ask; the builder's picture holds an ask that names a kept revision number, read by number), in build. | settled in H1 once delivered |