|
|
|
@@ -8,6 +8,7 @@ decisions:
|
|
|
|
|
- "ADR 0667"
|
|
|
|
|
- "ADR 0666"
|
|
|
|
|
- "ADR 0596"
|
|
|
|
|
- "ADR 0564"
|
|
|
|
|
- "ADR 0267"
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
@@ -16,7 +17,7 @@ decisions:
|
|
|
|
|
One file of milestone G's part of [design 47](../47-delivery-from-commit-to-delivered.md); the part opens at
|
|
|
|
|
[G.md](G.md). Its design lines are numbered across every file of the part and cited as "design 47 G §n".
|
|
|
|
|
|
|
|
|
|
*§718 to §731 come from milestone G's live delivery of 2026-11-17. The 24 pipelines of one catalog revision asked 96
|
|
|
|
|
*§718 to §732 come from milestone G's live delivery of 2026-11-17. The 24 pipelines of one catalog revision asked 96
|
|
|
|
|
composition runs, one per pipeline and machine, and 80 more when they were asked again. Each run kept its own copy of
|
|
|
|
|
a node's input of 1.1 to 1.5 MB in the assigner's state `inputs`, which reached its 64 MiB cap twice. The indexer's
|
|
|
|
|
and the teller's same failing tests failed once per artifact. The operator, 2026-11-17 about 10:20 CET: "In G, now".
|
|
|
|
@@ -65,9 +66,10 @@ domain of 2026-11-17 was answered by the lead in A-466 to A-466l (G-22), each ci
|
|
|
|
|
- **`could not run` is never read.** A step that finds an ended run whose outcome is `could not run` starts a new
|
|
|
|
|
run, replacing the key by compare-and-set; its former readers have already ended `could not run` with it.
|
|
|
|
|
- **The bound.** A run whose `ask` has no `step-ended` within the bound of the step that started it (the step's own
|
|
|
|
|
bound key with its time to live, A-77, A-101) ends `could not run`, naming the ask and the bound, and every reader
|
|
|
|
|
bound key with its time to live, A-77, A-101; A-466n) ends `could not run`, naming the ask and the bound, and every reader
|
|
|
|
|
with it. The end is heard on the assigner's durable consumer of the build seat's `step-ended` (A-240); the assigner
|
|
|
|
|
never reads the build seat's state (ADR 0596).
|
|
|
|
|
never reads the build seat's state (ADR 0596). A composition step's bound is the assigner's setting
|
|
|
|
|
`composition-step-bound`, default 30 minutes (the step bound of 2026-10-26).
|
|
|
|
|
- §721 **A machine's verdict names the modules it blames.** (ADR 0666 §17; A-452, A-466g, A-466h; principles 10, 3, 7
|
|
|
|
|
and 11) The composer's verdict of a machine (mesh-delivery-sdk's `composer.Machine`, answered by the node-engine's
|
|
|
|
|
`mesh-compose`) gains `blamed`, a list of `{module, problem}`.
|
|
|
|
@@ -140,7 +142,8 @@ domain of 2026-11-17 was answered by the lead in A-466 to A-466l (G-22), each ci
|
|
|
|
|
|
|
|
|
|
The runner hears the run's end as the build seat's `step-ended` of its `ask`, on its durable consumer, as it hears
|
|
|
|
|
every step (§24). A run whose `ask` has no `step-ended` within the bound of the step that asked it ends `could not
|
|
|
|
|
run`, as §720 has it, and every reader with it. At its start the runner takes up again each key with no `ended`, by its
|
|
|
|
|
run`, as §720 has it (A-466n), and every reader with it. A test step's bound is the runner's setting
|
|
|
|
|
`test-step-bound`, one per level, its default its level's existing run bound. At its start the runner takes up again each key with no `ended`, by its
|
|
|
|
|
`ask` and that bound. It deletes a key once the time its setting `test-runs-kept`, default 7 days, names has passed
|
|
|
|
|
since its `ended`, in the step log's order as §330 ages its `pipelines`, and deletes the run's output object with the
|
|
|
|
|
key, after the last reader's end. At the cap no run is asked, and the step ends `could not run`, naming the fill, as
|
|
|
|
@@ -193,13 +196,31 @@ domain of 2026-11-17 was answered by the lead in A-466 to A-466l (G-22), each ci
|
|
|
|
|
|
|
|
|
|
A step that names `shared` names its own build-input fingerprint beside it, as every `step-ended` does (§73). A
|
|
|
|
|
composition step's `step-started` is said by the runner when it asks the assigner, before any run is chosen, so it
|
|
|
|
|
cannot name the runs' asks; the assigner's `step-progress` carries them instead, and the watchman times a composition
|
|
|
|
|
step from that (§496, A-262).
|
|
|
|
|
cannot name the runs' asks; the assigner, the part that knows them, names them in its `step-progress`, and the
|
|
|
|
|
watchman times a composition step from that (§496, A-262, A-466m).
|
|
|
|
|
- §730 **What runs in flight, and going back.** (§65, §78; ADR 0666 §19, §24; ADR 0667 §9; A-466k; principle 3) A
|
|
|
|
|
composition step or test step asked before the new assigner or the new runner runs ends by the path it was asked
|
|
|
|
|
under, one run per step; composition runs and test runs are made only for steps asked after the new part runs. A
|
|
|
|
|
return to an earlier build (§78) leaves `composition-runs` and `test-runs` unread; their readers are ended `could not
|
|
|
|
|
run` by the bound of §720 and §725.
|
|
|
|
|
run` by the bound of §720 and §725 once the new build runs again. Until then the earlier build applies no such bound,
|
|
|
|
|
and a reader standing still is said by the watchman as `pipeline-stands`, by §732 (A-466o).
|
|
|
|
|
- §732 **The watchman times every step that reads a run.** (§75, §496, §602; ADR 0564 §2, §4; ADR 0666 §24; A-466o;
|
|
|
|
|
principles 3 and 1) §75 and §496 time each pipeline step from its `step-started` or its latest `step-progress`, but
|
|
|
|
|
the watchman on main times only a build seat's running ask (its `ask-taken` and `step-progress`) and a step queued
|
|
|
|
|
for a build node; a step whose run has ended, or a composition step waiting on the assigner, is timed by nothing.
|
|
|
|
|
From G the watchman also:
|
|
|
|
|
- **hears** the runner's `step-started` and `step-ended` of every pipeline step (it consumes them already, for the
|
|
|
|
|
build capacity), and `mesh-wants`' `step-progress`, a `consumes` entry its manifest gains;
|
|
|
|
|
- **keeps** each started step with no `step-ended` in memory under `<pipeline>/<step>`, its clock begun at its
|
|
|
|
|
`step-started` and begun again at each `step-progress` whose `ask` is the step's own ask (§496) or an ask its
|
|
|
|
|
`shared` names (§729), and at the `step-ended` of the run's ask a test step names;
|
|
|
|
|
- **raises** `pipeline-stands` for that step when its clock passes the watchman's existing five-minute progress bound
|
|
|
|
|
(§75), naming the pipeline, the step and the ask it last heard of, and clears it at the step's `step-ended`. A
|
|
|
|
|
step said waiting on a person, or queued for a build node (§86), is owed no progress, as today;
|
|
|
|
|
- **seeds** its open steps at its start from the runner's `stands`, as §75 has it.
|
|
|
|
|
|
|
|
|
|
So a reader that neither the assigner nor the runner ends, after a return to an earlier build or any fault, is said
|
|
|
|
|
within five minutes of its last sign of life.
|
|
|
|
|
- §731 **How it is checked.** Tests 108 and 109.
|
|
|
|
|
- **Whole (assigner, mesh-delivery), test 108.** Two composition steps of one candidate started at once make one key,
|
|
|
|
|
one request and one run ask. Three composition steps of one revision on two machines start two runs, and each step
|
|
|
|
@@ -221,6 +242,9 @@ domain of 2026-11-17 was answered by the lead in A-466 to A-466l (G-22), each ci
|
|
|
|
|
leaves the ask to the other readers. At the cap a step ends `could not run`, naming the fill. A second revision with
|
|
|
|
|
the same digests runs a failed test again. `runner_test_runs_drop` deletes the key and its output object, and a
|
|
|
|
|
reader-only account calling it is refused.
|
|
|
|
|
- **Whole (watchman), tests 108 and 109.** A composition step whose `mesh-wants` `step-progress` stops raises
|
|
|
|
|
`pipeline-stands` within five minutes; a test step whose run's ask ended with no `step-ended` of the step raises it
|
|
|
|
|
five minutes later; each clears at the step's `step-ended`; a step waiting on a person raises nothing.
|
|
|
|
|
- **Live.** In the first publish after G's delivery, the composition run asks of each revision number at most its
|
|
|
|
|
machines, read with `assigner_compositions` and `assigner_inputs`; each module's test steps run once per level, read
|
|
|
|
|
with `runner_test_runs`.
|
|
|
|
|