The assigner follows a kept composition's new digest, so a want held at an earlier build gets today's config (issue 1945, ADR 0545) #45

Merged

jschoubben merged 1 commits from fix/1945-kept-compositions-follow-config into main

2026-10-25 18:38:03 +00:00

Author	SHA1	Message	Date
jschoubben	73779a5dd1	Let a want held back at an earlier fingerprint follow that fingerprint's new revision (issue 1945, ADR 0545) mesh/delivery-group group fix/1945-kept-compositions-follow-config held: a member is held: novox/mesh-controller@ff3cc47027e0 (merged without a passing check: … Details mesh/delivery held for a person: merged without a passing check: only a person decides what follows Details 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.	2026-10-25 18:24:44 +01:00