A merge of a base rebuilds what stands on it #193

2026-10-01T14:09:40Z

mesh-admin commented

2026-10-01 14:09:40 +00:00

The controller knew which modules were built against which base artifacts (BuiltAgainst) and used it only when asked (build --on). A merge that rebuilt the runtime image today said "one module already built from it" and left forty-two modules on the old image until they were asked for by hand, twice (hq issue 186).

The merge handler now takes every catalogued module standing on what moved, through every layer, into the same rebuild, in base order (dependentsOf, then the existing orderByBases), and says so. Unit test dependents_test.go; make check on the branch.

Known cost, unchanged by this: the merge handler builds inside the receive loop (hq issue 184), so a runtime-image merge now holds the loop for the length of the wave rather than leaving the mesh half-rebuilt.

The controller knew which modules were built against which base artifacts (`BuiltAgainst`) and used it only when asked (`build --on`). A merge that rebuilt the runtime image today said "one module already built from it" and left forty-two modules on the old image until they were asked for by hand, twice (hq issue 186). The merge handler now takes every catalogued module standing on what moved, through every layer, into the same rebuild, in base order (`dependentsOf`, then the existing `orderByBases`), and says so. Unit test `dependents_test.go`; `make check` on the branch. Known cost, unchanged by this: the merge handler builds inside the receive loop (hq issue 184), so a runtime-image merge now holds the loop for the length of the wave rather than leaving the mesh half-rebuilt.

mesh-admin added 1 commit 2026-10-01 14:09:40 +00:00

A merge of a base rebuilds what stands on it 853c63b181

The controller knew which modules were built against which base artifacts and used it only when asked
(build --on). A merge that rebuilt the runtime image left forty-two modules on the old image until
somebody asked, twice, by hand (hq issue 186). The merge now takes every module standing on what moved,
through every layer, into the same rebuild, in base order — the same rebuild the flag does, asked by
the merge that made it necessary.

mesh-admin merged commit 7e701c0db2 into main

2026-10-01 14:12:32 +00:00

mesh-admin deleted branch fix/a-merge-of-a-base-rebuilds-what-stands-on-it

2026-10-01 14:12:32 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#193