mesh-controller

Author	SHA1	Message	Date
jschoubben	bc80683b9e	Count the work the take-ins start in the background, so a test's mesh closes only once that work has ended (issue 1851, A5-A7; issue 1790, D3)	2026-10-22 20:41:30 +02:00
jschoubben	ea3c8ad7f6	Register a new module from the builder's first done key and ask no first build; its condition reads the key and names a manifest word this controller does not read (issue 1851, A5a, A5b)	2026-10-22 19:05:04 +02:00
jschoubben	1e9b87e03a	Hold every refused module of a first merge and ask each again by its own path (issue 1173) mesh/merge-gate head 1e9b87e03acd merged into trunk b8f77577fed2 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head 1e9b87e03acd merged into trunk b8f77577fed2 — pass: its merge-check.sh passed Details mesh/delivery delivered Details mesh/check failed: integration: github.com/novox/mesh-controller/internal/identity.TestACertificateChainsToTheMeshsOwnAuthority: authority_test.go:45:… A held merge was asked again by the rule of a first merge, which finds nothing once a sibling module of the same merge registered, so it stayed held forever; and a second refusal in a merge already held fell through to a failed build. The hold now keeps a list of module, path and word, a refusal in a held waiting merge joins it, and the delivery of build-agent asks each held path again on the merge's Approve warrant.	2026-10-22 16:50:06 +02:00
jschoubben	4538d05732	Ask a held first build again when a delivery of build-agent ends (issue 1173) ADR 0482 section 5: the build waiting for a build-agent that reads its manifest is asked once the plan delivering it ends.	2026-10-22 16:19:45 +02:00
jschoubben	980d396d40	Keep a first merge whose manifest word the running build-agent does not read, and name it (issue 1173) ADR 0482 section 5: a merged manifest the running reader refuses waits for the newer reader, never failed.	2026-10-22 16:18:39 +02:00
jschoubben	ef0ca69cb0	The first build of a module a merge adds on the operator's Approve passes the guard of a build through a verb on the warrant it checked (issue 1146, AC9)	2026-10-19 00:48:56 +02:00
jschoubben	e621e15d2f	Its comment names D18 too (issue 1146) mesh/merge-gate head e621e15d2f5d merged into trunk b1cfb85f86ed — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head e621e15d2f5d merged into trunk b1cfb85f86ed — pass: its merge-check.sh passed Details mesh/delivery delivered Details	2026-10-19 00:20:31 +02:00
jschoubben	a08498b240	Name the waiting first merge's probe D18: designs 06 and 54 already name probe D17 (issue 1146)	2026-10-19 00:20:20 +02:00
jschoubben	39ae7de6d3	Say a first merge that waits past ten minutes for mesh-delivery's word, with probe D17 (issue 1146, AC8)	2026-10-19 00:19:03 +02:00
jschoubben	4e12fc19b7	A first merge into a new repository waits kept for mesh-delivery's word, and the word's arrival asks the builds, with no timer; AC7 on the bus in both orders (issue 1146)	2026-10-19 00:16:36 +02:00
jschoubben	19f15d8ea0	A merge on the operator's Approve into a repository the mesh builds nothing from asks the first build of the modules it holds (issue 1146, AC6, AC7)	2026-10-19 00:11:52 +02:00