Issue 218: a mesh seat is answered by a module on a machine that does not hold it #338

Merged
mesh-admin merged 1 commits from issues/218-a-mesh-seat-answered-by-a-non-holder into main 2026-10-03 21:25:27 +00:00
Contributor

The mesh-store seat (scope mesh) has one recorded holder, postgres on the control machine, yet postgres on the other machine also serves and announces its verbs; a store question was answered from the wrong database. Seen through the new discovery console. Where to look and the check that would hold it are in the report.

The mesh-store seat (scope mesh) has one recorded holder, postgres on the control machine, yet postgres on the other machine also serves and announces its verbs; a store question was answered from the wrong database. Seen through the new discovery console. Where to look and the check that would hold it are in the report.
mesh-admin added 1 commit 2026-10-03 21:25:23 +00:00
mesh-admin merged commit d362155401 into main 2026-10-03 21:25:27 +00:00
mesh-admin deleted branch issues/218-a-mesh-seat-answered-by-a-non-holder 2026-10-03 21:25:28 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#338