A failed mover is started again at the head; a reopening pins its revision again (H-A-479) #331

Merged
mesh-tools merged 4 commits from fix/runner-start-modules into main 2026-11-22 15:34:08 +00:00
Member

Design lines

hq branch design/47-H1-answers-59 (head 364552d2), 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md: H-A-479 (1) and (2), its addendum (1) and (2), its second and third addenda.

What changed

  • Seat mesh-pipeline-runner, form 8: the start verb takes modules; exactly one of module or modules is given. Contract regenerated (Go and TypeScript).
  • Pipeline runner, start with modules: the named modules whose newest entry has no passed pipeline are started at the head's revision, at the take-in's tiers, keyed <branch>.<revision>.again.<n> (n from 1, unbounded, written on absence). A module whose newest entry passed, that the head holds no entry of, or whose head entry a pipeline still runs ("its pipeline is running") is refused by name, nothing started. Every key-form list (the sweep's, a release's, the mover keys') reads the new form.
  • Pipeline runner, a rerun reopening an ended pipeline: reads its revision fresh through the catalog seat's revision verb and is refused by name when it is gone ("its revision is gone; start the mover again at the head"), and when another open delivering pipeline carries one of its movers at the same revision. Once reopened it says its pipeline-started before the step is asked again, so the indexer pins the revision until its next end.
  • Indexer: a pipeline ending not passed withdraws only the reservations of its own movers (read from the movers its pipeline-ended carries), and the revision's gathering only when none is left.
  • Pipeline tools: the start tool passes modules.

Tests

  • verbs_test.go, testruns_test.go, candidate_test.go: start with modules (passed, absent, running, again key forms through the branch's key forms, a release written into a passed again pipeline), a reopening's refusal when its revision is gone or another pipeline builds its mover, pipeline-started said before the rerun.
  • repin_test.go: own movers withdrawn; the gathering kept while another pipeline's reservation is left, removed with the last.
  • verbtools_test.go: the tool's modules argument.
  • Unit suites pass; integration tests compile (go vet -tags integration). Three review rounds.

Reviewed-by: mesh-code-reviewer@shanks at dca2545eb7
Pushed-by: lead-47@shanks

Group: mesh-delivery #330 + #331 + #332 (one merge call)

## Design lines hq branch `design/47-H1-answers-59` (head 364552d2), `03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md`: H-A-479 (1) and (2), its addendum (1) and (2), its second and third addenda. ## What changed - **Seat `mesh-pipeline-runner`, form 8**: the start verb takes `modules`; exactly one of `module` or `modules` is given. Contract regenerated (Go and TypeScript). - **Pipeline runner, start with modules**: the named modules whose newest entry has no passed pipeline are started at the head's revision, at the take-in's tiers, keyed `<branch>.<revision>.again.<n>` (n from 1, unbounded, written on absence). A module whose newest entry passed, that the head holds no entry of, or whose head entry a pipeline still runs ("its pipeline <key> is running") is refused by name, nothing started. Every key-form list (the sweep's, a release's, the mover keys') reads the new form. - **Pipeline runner, a rerun reopening an ended pipeline**: reads its revision fresh through the catalog seat's `revision` verb and is refused by name when it is gone ("its revision <r> is gone; start the mover again at the head"), and when another open delivering pipeline carries one of its movers at the same revision. Once reopened it says its pipeline-started before the step is asked again, so the indexer pins the revision until its next end. - **Indexer**: a pipeline ending not passed withdraws only the reservations of its own movers (read from the movers its pipeline-ended carries), and the revision's gathering only when none is left. - **Pipeline tools**: the start tool passes `modules`. ## Tests - `verbs_test.go`, `testruns_test.go`, `candidate_test.go`: start with modules (passed, absent, running, again key forms through the branch's key forms, a release written into a passed again pipeline), a reopening's refusal when its revision is gone or another pipeline builds its mover, pipeline-started said before the rerun. - `repin_test.go`: own movers withdrawn; the gathering kept while another pipeline's reservation is left, removed with the last. - `verbtools_test.go`: the tool's `modules` argument. - Unit suites pass; integration tests compile (`go vet -tags integration`). Three review rounds. Reviewed-by: mesh-code-reviewer@shanks at dca2545eb71d7100b0d423c8941f12d9e36e6d42 Pushed-by: lead-47@shanks Group: mesh-delivery #330 + #331 + #332 (one merge call)
mesh-tools added 4 commits 2026-11-22 15:33:24 +00:00
A module whose pipeline failed at an unchanged entry was never carried again
until its fingerprint moved, since start refused the head whose pipeline
existed. The start verb now takes modules: the named modules whose newest
entry has no passed pipeline are started at the head's revision, at the
take-in's tiers, keyed <branch>.<revision>.again.<n> (n from 1, written on
absence); a module whose newest entry passed, or that the head holds no
entry of, is refused by name, nothing started. Exactly one of module or
modules is given. The new key form is read by every key-form list (the
sweep's, a release's, the mover keys'). The runner seat's form is 8; the
contract is regenerated.

Builds: design 47 H2 H-A-479, H-A-479 addendum (1)
The indexer pins a pipeline's revision from pipeline-started to
pipeline-ended, so a rerun of a step in an ended pipeline (main.258's
composition at 14:41, after its end at 14:15) asked a step against a
revision the catalog had already removed. A rerun of an ended delivering
pipeline now reads its revision fresh through the catalog seat's verb
revision first and is refused by name, nothing asked, when it is gone
("its revision <r> is gone; start the mover again at the head"); once
reopened it says its pipeline-started again, so the indexer pins the
revision until its next end.

Builds: design 47 H2 H-A-479, H-A-479 addendum (2)
A pipeline ending not passed withdrew every reservation of its revision, so
an again pipeline's failure could withdraw the head's take-in pipeline's
reservations and the other way round. The indexer now withdraws only the
reservations of the ended pipeline's own movers, read from the movers its
pipeline-ended carries, and withdraws the revision's gathering only when
none is left. A start with modules is refused for a module whose head entry
a pipeline still runs ("its pipeline <key> is running"), and takes the next
n without a bound. A rerun reopening an ended pipeline says its
pipeline-started before the step is asked again, so the revision is pinned
before anything reads it. Tests now cover the again form through the
branch's key forms and a release written into a passed again pipeline.

Builds: design 47 H2 H-A-479 second addendum, H-A-479 addendum (2); review round 1
A rerun that would reopen an ended pipeline while another open delivering
pipeline carries one of its movers at the same revision is refused with
"its pipeline <key> is running", nothing asked, so one entry is never built
side by side. Tests now cover the two paths review round 2 found untested:
the indexer keeps a revision's gathering while another pipeline's
reservation is left and removes it with the last, and a test step's rerun
reopening an ended pipeline says pipeline-started before its run is started
again.

Builds: design 47 H2 H-A-479 third addendum, H-A-479 second addendum, H-A-479 addendum (2); review round 2
mesh-tools merged commit 7dd2891f32 into main 2026-11-22 15:34:08 +00:00
mesh-tools deleted branch fix/runner-start-modules 2026-11-22 15:34:09 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-delivery#331