jschoubben
73779a5dd1
mesh/delivery-group group fix/1945-kept-compositions-follow-config held: a member is held: novox/mesh-controller@ff3cc47027e0 (merged without a passing check: …
mesh/delivery held for a person: merged without a passing check: only a person decides what follows
mesh/check failed: integration: github.com/novox/mesh-controller/cmd/mesh-controller.TestTheDeclarationsStreamGoesOnceEveryNodeRunsTheNewEngine: with …
The controller now composes a module's kept compositions again when its config changes, so going back keeps today's config. A want held back at an earlier fingerprint kept the digest it was first written with, and the node applied the old revision from the bucket's history: on g14 a rollback of mesh-build-go put its capacity back to 0. The want now names the new digest, asked through the record hold as any move of a record module is. A want held at F by the rules still waits for them, as a new fingerprint does (ADR 0539 §5). Research 072: milestone 2, the composer reacting to the change of an input.
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.