Undo: claiming mesh-broker made lavinmq unbuildable #118

2026-09-27T19:53:43Z

jschoubben commented

2026-09-27 19:53:43 +00:00

Reverting my own change from an hour ago. Putting the mesh-broker claim back on lavinmq does not restore the holder — it stops lavinmq being registered at all:

lavinmq claims mesh-broker, whose holder answers for "mesh-bus",
and lavinmq does not provide "mesh-bus" at mesh scope

That refusal is itself a bug, fixed in mesh-controller — it came from a copy of the seat table compiled into the build machine rather than from the store, which says the seat answers for amqp, which lavinmq does provide. But the refusal is what the mesh does today, so this claim has to come back out until the controller carrying that fix is deployed.

The seat being empty remains the live fault. It is fixed by the controller change, not here.

Reverting my own change from an hour ago. Putting the `mesh-broker` claim back on lavinmq does not restore the holder — it stops lavinmq being registered at all: ``` lavinmq claims mesh-broker, whose holder answers for "mesh-bus", and lavinmq does not provide "mesh-bus" at mesh scope ``` That refusal is itself a bug, fixed in mesh-controller — it came from a copy of the seat table compiled into the build machine rather than from the store, which says the seat answers for `amqp`, which lavinmq does provide. But the refusal is what the mesh does *today*, so this claim has to come back out until the controller carrying that fix is deployed. The seat being empty remains the live fault. It is fixed by the controller change, not here.

jschoubben added 1 commit 2026-09-27 19:53:43 +00:00

Undo: lavinmq cannot hold mesh-broker, and claiming it makes lavinmq unbuildable f97b7dd544

Putting the claim back was wrong on its own terms. `mesh-broker` delivers
`mesh-bus`, and a seat that delivers a provision may only be held by a module that
provides it — so the claim is refused at registration:

  lavinmq claims mesh-broker, whose holder answers for "mesh-bus",
  and lavinmq does not provide "mesh-bus" at mesh scope

Which means the merged claim does not restore the holder, it stops lavinmq being
built at all. Removed again.

The seat being empty is still the live fault, and it has only one valid answer: the
holder must provide `mesh-bus`, and the module that does is nats. Recorded against
the rollout, because it moves a step that was optional into the critical path.

jschoubben merged commit 6e5b2557ba into main

2026-09-27 19:53:49 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#118