From 885b1c54fc7a840aa86b529e3547916e9c2f980f Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 20:28:50 +0100 Subject: [PATCH] Design 47 H: section 10, finding 181 --- .../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 bb73672e..a1c8f8da 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 @@ -697,3 +697,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | One more pipeline fell to the store's half-minute absence (row 177): the re-pin pipeline that followed the tool runner's ended failed at 19:43, with many build steps failed and lint steps could-not-run, because the builder's fetch of each source met the forge's 401 in that minute and the builder read the refusal as the build's verdict; the builder. Meanwhile the pipeline of 856 steps holds the slot since 19:46, and the catalog repository's pipeline of 36 movers waits behind it (rows 170, 175 and 177). Owed, by H-A-301, the same kind as H-A-296 and H-A-300: a step whose fetch meets the forge away is asked again with a back-off until its bound, and a fetch failure is said apart from a build failure. | H2 (owed) | | Forty minutes after proof 2 (row 172) the home server's tool runner dropped out of discovery: its node-engine restarts it every 20 to 50 seconds, because the composition key for the tool runner at its new fingerprint alternates between two digests written in turn by two composition runs, one resource (the runtime process) differing; the mesh MCP server on the operator's desktop dropped at 20:16 too, and the control-node's tool runner missed a round of discovery, so the other machines' keys are being read; the stale writer is being found and dropped with the assigner's own tool, as the recovery of the moment; the holder of the seat mesh-wants (`mesh-delivery-assigner`), the node-engine and the tool runner (`node-tools`). The same read found the pipeline of 856 steps (row 178) not stalled: its validate run took 25 minutes, and its last test steps passed at 20:15; and a tool fault: the build seats' steps read tool answered empty on every node while steps ran (rows 172, 176 and 178). Owed, by H-A-302: a composition key written by the newest run only; a run whose pipeline ended writes nothing more; the node-engine applies only a newer write and names it; and the steps read tool answers the steps state. | open (the flapping); H2 (the rule, the tool) | | Row 179's cause was not a stale run: no second composition run writes the key; on three of four machines the node-engine composes the tool runner's self-want itself, and while the grants part does not answer ("withheld unknown") every compose differs in the runtime process, so the node-engine writes a new revision and restarts the tool runner at each compose (every 20 to 50 seconds on the home server, slower on the operator's desktop and the control-node; the laptop, whose compose got the grants answer, is steady); the control-node's tool runner serves the grants answer, which closes the loop; the node-engine and the tool runner (`node-tools`). Settled by H-A-303, which amends H-A-302 (a withheld part keeps the running composition's part and writes no revision; the node-engine applies only a difference in a part it could read; the withheld part is said once), in build in the node-engine; the recovery of the moment, a held put of the tool runner on the home server through the assigner's tool, is being tried. Beside this, the operator decided at 20:24 (the relaying session wrote 20:35), through the session on their desktop, that the packet filter module gets standing control verbs on the seat node-packet-filter (allow, disallow and allowed, with an optional expiry) beside the ports derived from declarations, so design 08 ยง4 and the seat's verbs change (H-A-304; the decision record amending ADR 0170 is proposed; its first use is tcp 8000 on the LAN interfaces of the operator's desktop); its build runs beside H1's tail (rows 172, 176 and 179). | open (the flapping); other (the packet filter's verbs) | +| The mechanism of row 180's loop, read in the node-engine's code and the home server's journal: the self-compose never asks the seat mesh-grants; what goes unanswered is a module's entry or its registry versions, and a module held for that is composed as a stand-in whose slice of the tool runner's runtime process is rebuilt from what runs without its fingerprint and files words, so the process's module list and words differ from pass to pass and the node-engine restarts the tool runner each time ("restarted because its unit's Environment MESH_TOOL_MODULES changed"); the node-engine and the tool runner (`node-tools`). Settled by H-A-306, which amends H-A-303 (a withheld part is every input a compose asks and does not get; a held module's slice is copied verbatim from the running process; a withheld part is said once), in build in the node-engine. The recovery of the moment works: a held put of the tool runner on the home server through the assigner's tool at 20:22 stopped the loop (one restart at 20:26, then steady); the same hold goes on the operator's desktop and the control-node, to be released when the node-engine's fix is delivered (rows 172, 179 and 180). Owed: a read of composed values by resource. | open (the fix in build); H2 (the read) |