Live after the push at 14:43Z: mesh-postgres on the control node restart-looped with postgres cannot serve mesh-store.databases: a module serves its own tools. Its broker credential dates from 2026-09-28 and carries no claims (a minted secret is written once), so the runtime took the mesh-store registration for the module's own and refused the key fatally. Now a registration under a name that is neither the module nor a seat its credential claims is named in the log and left out; the module's own tools serve. Test added; suite green. The credential itself is re-issued separately (module issue postgres --node …).
Live after the push at 14:43Z: `mesh-postgres` on the control node restart-looped with `postgres cannot serve mesh-store.databases: a module serves its own tools`. Its broker credential dates from 2026-09-28 and carries no `claims` (a minted secret is written once), so the runtime took the `mesh-store` registration for the module's own and refused the key fatally. Now a registration under a name that is neither the module nor a seat its credential claims is named in the log and left out; the module's own tools serve. Test added; suite green. The credential itself is re-issued separately (`module issue postgres --node …`).
A module implementing a seat its credential does not (yet) claim registered tools under the seat's
name; the runtime treated them as the module's own, refused to serve another module's key, and the
whole runtime restarted in a loop — postgres on the control node, 2026-10-01, whose credential predated
the claims. Such a registration is now named in the log and left out; the module's own tools serve.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Live after the push at 14:43Z:
mesh-postgreson the control node restart-looped withpostgres cannot serve mesh-store.databases: a module serves its own tools. Its broker credential dates from 2026-09-28 and carries noclaims(a minted secret is written once), so the runtime took themesh-storeregistration for the module's own and refused the key fatally. Now a registration under a name that is neither the module nor a seat its credential claims is named in the log and left out; the module's own tools serve. Test added; suite green. The credential itself is re-issued separately (module issue postgres --node …).