From 30d83353ca0b5cd871439357bba45df0b682efbe Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 23:12:20 +0100 Subject: [PATCH] Design 47 H: section 10, finding 88 by H-A-210 --- .../01-to-be/47-milestones/H-deliver-the-delivery-system.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 dba18aa0..64ff1cd7 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 @@ -604,4 +604,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | A test step of an entry whose package has no version yet went out without that pin and was refused; the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-206 (a Go artifact's test steps wait for their pins as the build does, "waits on the publish of "), in build in the runner. | settled in H1 once delivered | | The Node build module's tool that lists its running steps does not list delivery asks (the builder's own asks), so the check "no running step" before a hand restart cannot see them; the Node build module. Owed: the list names every ask the module runs, whoever asked. | H2 | | A test step held for a pin not yet published had nothing to end it once its build passed (the builder had read the registry and pinned it), so with one pipeline at a time the queue would stop; the pipeline runner (`mesh-delivery-pipeline`) and the builder. Settled by H-A-207 (the build's end reports the pins it built with, the seat mesh-builds' end carrying `packages`, and the runner asks the held steps with them), in build. | settled in H1 once delivered | -| The reading of the module graph (H-A-201) runs at a take-in, which applies a repository whole, so repositories with no merge since the rule changed kept their modules' direct requirements only, and no tool took a repository in again; the indexer (`mesh-delivery-indexer`). Settled by H-A-208 (the tool `indexer_take_in_again` takes a repository's current source revision in again), in build. Owed: a change of the indexer's rules recomputes every repository by itself at the indexer's start; the tool is the hand form of that. | H2 | +| The reading of the module graph (H-A-201) runs at a take-in, which applies a repository whole, so repositories with no merge since the rule changed kept their modules' direct requirements only, and no tool took a repository in again; the indexer (`mesh-delivery-indexer`). Settled by H-A-208 (the tool `indexer_take_in_again`), H-A-209 and H-A-210: the take-in again keeps no catalog revision and asks no gate; it re-reads the repository's kept requirements at its merge commit and recomputes the modules state as a publish re-pin does; in build. Owed: a change of the indexer's rules recomputes every repository by itself at the indexer's start; the tool is the hand form of that. | H2 |