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 6df6d951..0b765950 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 @@ -659,4 +659,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | Row 138's fix was built in the indexer and the pipeline runner, reviewed in three rounds and merged at 13:22 as its own pipeline; the rounds found a finding that never cleared, three design points (a pending proposal is skipped; a module the seed left out is not registered by the graph; the branch is the one the siblings hold alike, else the repository's default) and an untested rule, settled by H-A-263, H-A-264, H-A-265 and H-A-266 (row 138); the indexer (`mesh-delivery-indexer`) and the pipeline runner. Its hand packs go onto the control-node next, so the indexer's start pass registers the four modules itself. Owed: a read of the registrations store in one call. | H1 | | The hand packs of row 140 went onto the control-node at 13:27 and 13:28: the indexer's start pass registered a fifth unregistered module at once (a networking contracts module nobody had noticed) and skipped the four whose proposals were pending, as H-A-265 asks; the lead had those four proposals dropped with the indexer's own tool (the operator's four asks cancelled with them), and the next start registered the four at 13:28:29, each at version 1 with the warrant "module graph". The pipeline runner (`mesh-delivery-pipeline`) at its start said 115 movers of proof 2's pipeline "have no registration yet" before its view of the registrations had loaded, then placed 1048 of their steps at 13:30:55: a fault of the start order of the runner's new check, loud and passing (rows 138, 139 and 140); the indexer (`mesh-delivery-indexer`) and the pipeline runner. Owed: the check waits for the view's first read. | H1 (the registrations); H2 (the start order) | | Proof 2's pipeline ran from 13:13 with over a thousand steps: the SDK's new version 0.1.29 was published, and the build node built modules against it from 13:58; the tool runner's six steps passed in it. Then the revision of the register-at-take-in merge (13:22) and the indexer's recomputes moved the tool runner and about a hundred other movers to the newer pipelines, as the rule says, so the proof's acceptance follows the tool runner's want on each machine rather than one pipeline's end; the superseded pipeline keeps running its remaining movers (rows 136, 139 and 141); the pipeline runner (`mesh-delivery-pipeline`). Owed: a read of a pipeline's record for one mover's steps (62 KB) still exceeds a reader without a shell, the lighter read of row 124's kind. | H1 | -| The pipeline that carried the tool runner after the move of row 142 ended failed at 15:03:55 on the required steps of three modules of the catalog repository, none of them the tool runner's (its build, tests, validate and composition all passed, its release 0.1.37 reserved): the forge module's TypeScript build cannot find the contracts package it imports and uses fields its contracts type lacks, and its integration test of the whole seat fails; the bus module's integration test of the whole module fails on the subtest "the fill pass runs while the first view is asked", the one every developer tonight reported as failing at trunk and skipped (by the rule of the second failure, the kind is fixed now, not skipped again); and the registry's integration test of the whole module fails; so no pipeline wrote a passed end for the tool runner, and its want stays. Seen beside it: the earlier pipeline passed at 14:26, but the holder of the seat mesh-wants wrote no end for its eleven remaining movers (the SDK's want still names the morning's pipeline); and the builder has asked the registry to publish the tool runner's release again every few minutes since 14:50, with no "published" answered. Under reading (rows 104, 137 and 142); the forge module, the bus module, the artifact registry, the holder of the seat mesh-wants and the builder. | H1 | +| The pipeline that carried the tool runner after the move of row 142 ended failed at 15:03:55 on the required steps of three modules of the catalog repository, none of them the tool runner's (its build, tests, validate and composition all passed, its release 0.1.37 reserved): the forge module's TypeScript build cannot find the contracts package it imports and uses fields its contracts type lacks, and its integration test of the whole seat fails; the bus module's integration test of the whole module fails on the subtest "the fill pass runs while the first view is asked", the one every developer tonight reported as failing at trunk and skipped (by the rule of the second failure, the kind is fixed now, not skipped again); and the registry's integration test of the whole module fails; so no pipeline wrote a passed end for the tool runner, and its want stays. Seen beside it: the earlier pipeline passed at 14:26, but the holder of the seat mesh-wants wrote no want for its eleven remaining movers (its record of the pipeline's end names none of them; the SDK's want still names the morning's pipeline); and the builder has asked the registry to publish the tool runner's release again every few minutes since 14:50, with no "published" answered. Under reading (rows 104, 137 and 142); the forge module, the bus module, the artifact registry, the holder of the seat mesh-wants and the builder. | H1 |