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 776133ce..8b16aefc 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 @@ -551,3 +551,25 @@ desktop, with hand restarts), and these were met on the way. A row a lead answer | The seat node-files has no verb that reads a file's sha256, and its `copy` refuses another node (issue 903), so hand packs were copied by the lead's shell; node-files. | H2 | | The builder's unit written by hand on the desktop carries none of the manifest's setting variables, so its settings are the defaults; the builder's hand pack. | H1, the runbook | | The clean proofs of the runbook's step 7 are still owed: the first proof failed on the version race (settled by H-A-155), the second ran for the publish of the SDK packages; the freeze is not lifted (step 8). | H1 | + +Added by the lead at 19:50 CET, from the run of 18:40 to 19:50; a row met again names the row of 18:40 it adds to. + +| finding | milestone | +|---|---| +| The node-engine (`mesh-host`) asks the seat mesh-recovery for a restore point before it moves a data-holding module, and the recovery module is placed nowhere (H §456), so every such take-in was held for good; the node-engine. Settled by H-A-177 and H-A-178 (it moves without a point where no holder is placed and raises the finding `restore-point-missing`). | settled in H1 | +| A package module no machine holds (mesh-delivery-sdk) had a required composition step that could not run, so its pipeline could never pass (main.35, the second proof); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-179 (the step ends `nothing to run`, ADR 0682 §8). | settled in H1 | +| A module held for a failed restore point kept the hold across the node-engine's start, and no operator's ask was raised for it, so the hold was for good; the node-engine. Settled by H-A-180 (the hold's cause is judged again at the start and on every change of placements). | settled in H1 | +| The forge bridge kept each owed event whole in its state `performed`, filling its kept data to 51 MB of the template's 64 MiB (19,530 keys, the condition "kept data is filling up"); the forge bridge. Settled by H-A-181 and H-A-182 (the outcome, when, and the act's pull request; the act stays in the gate's stream `owed`). | settled in H1 | +| The finding `restore-point-missing` did not reach the conditions after the first move without a point: the finding's wiring to the condition keeper; the node-engine. | H2 | +| The recovery module is placed nowhere, and the assigner derives no placement from the holder of the seat mesh-broker (G §554); the assigner (`mesh-delivery-assigner`). | H2 | +| A pipeline record with 112 or 129 movers exceeds the bus's 1 MiB message limit once its steps are placed, so two pipelines were cancelled; the record's shape (steps per mover key) and the limit as a setting; the pipeline runner. | H2 | +| A change to the SDK package folds in about 112 importers and a change in the catalog repository about 60, so the first re-pin of those repositories cannot run until the pipeline record is reshaped (the row above); the pipeline runner. | H2 | +| Met again on the tool runner's pipeline: a superseded build makes the older pipeline fail instead of its mover leaving it (the row of 18:40 on a withdrawn build); the pipeline runner and the builder. | H2 | +| The gate's owed acts run at about ten times the design's estimate (about 80 note acts per delivery record per pull request), and the gate's own stream `owed` takes the same rate; the gate (`mesh-delivery-gate`). | H2 | +| The forge bridge's `bridge_owed` by pull request still reads every key of its state in the tool runner's process; the forge bridge. | H2 | +| A refused consumer creation is tried again for longer than the tools' wait for an answer, so a person sees a timeout instead of the refusal; the bus module's tools. | H2 | +| Met again: the SDK's finding write for an unhandled event waits up to 3 s on the bus inside the event loop, seen as a 90 s test (the row of 18:40); mesh-sdk. | H2 | +| Met again: the build node counts untagged tests into a module's integration count (the row of 18:40); the Go build module (`mesh-build-go`). | H2 | +| Met again: the step outputs store keeps 0 bytes, so a failed test's words are lost (the row of 18:40); the pipeline runner. | H2 | +| The proof of the runbook's step 7 is still owed: proof 1 failed on the version race, proof 2 twice, on stale pins and on the composition step of a module no machine holds (settled by H-A-179), both settled; the freeze is not lifted (step 8). | H1 | +| Four hand placements more (the distribution tools bundle, the assigner, the builder's program, the node-engine twice) and five hand restarts were needed to break circles, each said to the operator; the runbook. | H1, the runbook |