63bb53bb6bfaf7b53577de744c841138702288c8
The runner's settings pipelines-at-once (default 1, from 1 to 8) and pipelines-waiting-cap (default 64) are written to files by the manifest and read at the start; its state queue holds queue.next, waiting.<sequence> and running.<pipeline>. A start (a take-in's, a publish's, a hand start's, a run on request's) judged against the running keys alone either runs, its running key written after its pipeline, or is written waiting under the next sequence, its waiting key first, with no step asked, saying pipeline-started and wait-held step pipeline on pipelines-at-once. Every end, a cancel's too, deletes the running key and places the lowest sequence, which says wait-ended and has its steps placed (a run's from its candidate's newest revision). At the start a running key whose pipeline runs no more is deleted and the queue placed. The test runs' whole test sets pipelines-at-once 8, as its candidates run side by side. Builds: design 47 H §748; lead answers H-A-14, H-A-36, H-A-52, H-A-53, H-A-60, H-A-72, H-A-96 Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
mesh-delivery
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/repo-check (this repository's merge-check.sh) and mesh/merge-gate passed.
Description
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
36 MiB
Languages
Go
99.3%
JavaScript
0.7%