Issues 248, 249: the controller's event consumer replayed a week; a new state is refused until a push #100

2026-10-05T15:16:46Z

mesh-admin commented

2026-10-05 15:16:46 +00:00

248 (located, mesh-controller): the controller's EVENTS consumer delivered everything the stream holds (a week, 6 955 merges and build outcomes, one at a time), so the 15:17 merge and every build since went unseen; a missing consumer is made with the server's default, which issue 207 did not cover. Unblocked by hand on the operator's word; fix in the mesh-controller PR.
249 (open): a module's new state reaches every machine in its bundle before the grants to use it; and the merge delivers to every machine at once, so no machine can go first.

- 248 (located, mesh-controller): the controller's EVENTS consumer delivered everything the stream holds (a week, 6 955 merges and build outcomes, one at a time), so the 15:17 merge and every build since went unseen; a missing consumer is made with the server's default, which issue 207 did not cover. Unblocked by hand on the operator's word; fix in the mesh-controller PR. - 249 (open): a module's new state reaches every machine in its bundle before the grants to use it; and the merge delivers to every machine at once, so no machine can go first.

mesh-admin added 1 commit 2026-10-05 15:16:46 +00:00

Issues 248 and 249: the controller's event consumer replayed a week; a new state is refused until a push df2072aed5

248, located: a consumer made with the server's default replays the whole
stream, and the controller's held every new merge and build behind a week of
old ones. 249, open: a module's new state reaches its bundle before the
grants that let it use it.

mesh-admin merged commit 400ed8d396 into main

2026-10-05 15:27:24 +00:00

mesh-admin deleted branch issues/248-249-delivery

2026-10-05 15:27:24 +00:00

mesh-admin referenced this pull request

2026-10-06 20:25:29 +00:00

Issue 281: a tier sent one module at a time blamed a module for its machine #154

mesh-admin commented

2026-10-06 23:07:11 +00:00

Delivery novox/hq@400ed8d39618 — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/hq#100 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@400ed8d39618` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/hq#100 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben referenced this issue from a commit

2026-10-06 23:38:39 +00:00

Issue 282: a secret on a command line is kept in the runtime's events

mesh-admin referenced this pull request

2026-10-06 23:38:43 +00:00

Issue 282: a secret on a command line is kept in the runtime's events #160

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#100