To-be 45 in progress; issue 269: the controller cannot write a cancelled set #129

2026-10-06T01:04:42Z

mesh-admin commented

2026-10-06 01:04:42 +00:00

Playbook 04 for to-be 45 (ADR 0227): status: in-progress, code: names the owning repositories the design lists (mesh-controller, mesh-host, mesh-tools, mesh-catalog, mesh-lab). Phase 0 for mesh-controller and mesh-host is in novox/mesh-controller#78 and novox/mesh-host#32.

Issue 269 (located, mesh-controller): found while granting the controller its new buckets — a key-value write is a publish to the bucket's subject, which the controller's grant never covered for the work queues' cancelled sets, so cancel/clear time out. Reproduced against a server holding exactly the composed grant; fixed in the same two PRs.

00-META/checks/records.py, index.py, cycle.py pass.

Playbook 04 for to-be 45 (ADR 0227): `status: in-progress`, `code:` names the owning repositories the design lists (mesh-controller, mesh-host, mesh-tools, mesh-catalog, mesh-lab). Phase 0 for mesh-controller and mesh-host is in novox/mesh-controller#78 and novox/mesh-host#32. Issue 269 (located, mesh-controller): found while granting the controller its new buckets — a key-value write is a publish to the bucket's subject, which the controller's grant never covered for the work queues' cancelled sets, so `cancel`/`clear` time out. Reproduced against a server holding exactly the composed grant; fixed in the same two PRs. `00-META/checks/records.py`, `index.py`, `cycle.py` pass.

mesh-admin added 1 commit 2026-10-06 01:04:43 +00:00

To-be 45 in progress; issue 269: the controller cannot write a cancelled set a6c0f002a5

Phase 0 is being built in mesh-controller and mesh-host. Granting the
controller its own buckets showed that its grant never covered the work
queues' cancelled sets, so every cancel times out.

mesh-admin merged commit aa52a0b6bb into main

2026-10-06 07:19:15 +00:00

mesh-admin deleted branch feat/a-core-that-cannot-fail-silently-phase-0

2026-10-06 07:19:16 +00:00

mesh-admin commented

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

Delivery novox/hq@aa52a0b6bb0c — 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#129 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@aa52a0b6bb0c` — **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#129 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`.

mesh-admin referenced this pull request

2026-10-07 23:31:32 +00:00

Triage issues 279-298: resolve the fixed, with replays R292 and R298 #188

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#129