A push raises what a module hears, not only a start #132

2026-09-28T14:46:53Z

mesh-admin commented

2026-09-28 14:46:53 +00:00

No description provided.

mesh-admin added 1 commit 2026-09-28 14:46:54 +00:00

A push raises what a module hears, not only a start 878690697e

A module's declaration and its consumer are derived from the same records, and only one of them
followed a push: the consumers were raised when the control plane started serving, so a module that
gained a `consumes` was sent a declaration it could act on and a consumer that never delivered the
event — with nothing anywhere saying the two disagreed. Found on review: the catalogue's own replay
subscription was recorded, granted and never delivered.

Everything the raise does is idempotent, so a push may do it.

mesh-admin merged commit ce9e20fbbc into main

2026-09-28 14:46:55 +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#132