Design 47 H: section 10, finding 90
This commit is contained in:
@@ -606,3 +606,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 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`), 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 |
|
||||
| The pin kind (rows 62, 66, 72, 79, 81 to 85, 87, 88) was fixed one instance per round for five hours, against the rule "at the second failure of a kind, fix the kind"; the rule was then written whole as a specification with a gap table against the code ([H-pins-spec-and-gaps.md](H-pins-spec-and-gaps.md)): 35 lines, 24 built, 6 built otherwise, 1 contradicted, 2 missing, and 7 changes still missing (its section 8), the largest that a re-pin on a publish never became a revision or a mover (the "entry-missing" holds on wants), settled by H-A-211 (a re-pin is taken in as the next catalog revision of the same source); the indexer (`mesh-delivery-indexer`), the pipeline runner, the builder and the Go build module. The lesson for playbook 07: a kind met twice gets its specification before its third fix, and one owner across every part it touches. | H1 (the way of working); H2 for the owed items of the specification's section 8 |
|
||||
| A catalog revision's number equalled the gate's source revision by habit, so a re-pin had no number to keep its entries under, and the pipeline runner started a pipeline per published artifact (several per release) from its own hearing; the indexer (`mesh-delivery-indexer`), the seat mesh-catalog's definition and the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-212 and H-A-213: a revision's number is the indexer's own counter, with the gate's source as a field; a revision carries its call (`call`: take-in, release of a module version, or take-in again of a repository); one pipeline per release revision; the runner keys pipelines and reads revisions by number. In build by the one owner of the pin kind (row 89). | settled in H1 once delivered |
|
||||
|
||||
Reference in New Issue
Block a user