At 21:04 three newly assigned modules had no bus account; each was held, its bare stub kept RunsAs, ownRuntimes refused it, and that refused every module on novox (79) and ace (74): the fourth whole-node refusal of the day. ownRuntimes skips Stubbed modules; runtimeProcess gives no process for a held runtime; NoRuntimeToRunError{Held}; blames makes a held runtime the culprit. aHeldModuleOfItsOwnAccountNeverRefusesTheNode replays it.
Group fix/held-module-and-assigner-contract (mesh-sdk, mesh-host, mesh-delivery, mesh-catalog), issue 774. The lead merges once mesh/check and mesh/delivery-group are green (operator, 2026-10-30 20:41); mesh-sdk first.
Reviewed-by: rev-sweep@shanks at eff81f1220
At 21:04 three newly assigned modules had no bus account; each was held, its bare stub kept RunsAs, ownRuntimes refused it, and that refused every module on novox (79) and ace (74): the fourth whole-node refusal of the day. ownRuntimes skips Stubbed modules; runtimeProcess gives no process for a held runtime; NoRuntimeToRunError{Held}; blames makes a held runtime the culprit. aHeldModuleOfItsOwnAccountNeverRefusesTheNode replays it.
Group fix/held-module-and-assigner-contract (mesh-sdk, mesh-host, mesh-delivery, mesh-catalog), issue 774. The lead merges once mesh/check and mesh/delivery-group are green (operator, 2026-10-30 20:41); mesh-sdk first.
Reviewed-by: rev-sweep@shanks at eff81f1220e22ee6ba6c17cb036753a69a266a47
On 2026-10-30 at 21:04 mesh-self-check (ace) and mesh-conditions, mesh-healers (novox) were placed before
their bus accounts were issued. Each was held for "needs a secret called broker and none was made"; its bare
stub then lost its own secrets and was refused by ownRuntimes ("runs as its own account and declares no own
secret broker"), a refusal no culprit takes, so 74 modules on ace and 79 on novox failed. A held runtime's stub
met the same kind earlier today ("its build produced 0 bundle(s)").
Quick fix: let the bare stub keep its broker own secret, for this one rule.
Thorough fix (chosen, the fourth of the kind today): a held module's stand-in (Stubbed) has no runtime
composed at all, so no rule about its runtime, bundle or broker can refuse it: ownRuntimes passes it over and
runtimeProcess composes none for a held runtime (what runs of either is carried, as before). A module of its
own account left without its runtime by a held runtime is refused with a typed NoRuntimeToRunError, which makes
the held runtime the culprit, so those modules are held after it and the node composes the rest.
Deliverynovox/mesh-sdk@eff81f1220e2 — merged since 2026-10-30T21:17:41Z
Source — source.main moved to novox/mesh-sdk@b74e23f973. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
composed together: pass — the checker's verdict at the members' heads (e5a2974f3e1e)
Transitions
2026-10-30 20:31 (new) → proposed (announced): novox/mesh-sdk#142's head announced
2026-10-30 20:31 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-30 21:17 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-sdk@eff81f1220e2` — **merged** since 2026-10-30T21:17:41Z
**Source** — source.main moved to novox/mesh-sdk@b74e23f973ab. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Group** `fix/held-module-and-assigner-contract`: novox/mesh-catalog@b5475cfa5c3d, novox/mesh-delivery@8fe6442c4754, novox/mesh-host@62cfb45789c1, novox/mesh-sdk@eff81f1220e2
- composed together: pass — the checker's verdict at the members' heads (e5a2974f3e1e)
**Transitions**
- 2026-10-30 20:31 (new) → proposed (announced): novox/mesh-sdk#142's head announced
- 2026-10-30 20:31 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
- 2026-10-30 21:17 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
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.
At 21:04 three newly assigned modules had no bus account; each was held, its bare stub kept RunsAs, ownRuntimes refused it, and that refused every module on novox (79) and ace (74): the fourth whole-node refusal of the day. ownRuntimes skips Stubbed modules; runtimeProcess gives no process for a held runtime; NoRuntimeToRunError{Held}; blames makes a held runtime the culprit. aHeldModuleOfItsOwnAccountNeverRefusesTheNode replays it.
Group fix/held-module-and-assigner-contract (mesh-sdk, mesh-host, mesh-delivery, mesh-catalog), issue 774. The lead merges once mesh/check and mesh/delivery-group are green (operator, 2026-10-30 20:41); mesh-sdk first.
Reviewed-by: rev-sweep@shanks at
eff81f1220On 2026-10-30 at 21:04 mesh-self-check (ace) and mesh-conditions, mesh-healers (novox) were placed before their bus accounts were issued. Each was held for "needs a secret called broker and none was made"; its bare stub then lost its own secrets and was refused by ownRuntimes ("runs as its own account and declares no own secret broker"), a refusal no culprit takes, so 74 modules on ace and 79 on novox failed. A held runtime's stub met the same kind earlier today ("its build produced 0 bundle(s)"). Quick fix: let the bare stub keep its broker own secret, for this one rule. Thorough fix (chosen, the fourth of the kind today): a held module's stand-in (Stubbed) has no runtime composed at all, so no rule about its runtime, bundle or broker can refuse it: ownRuntimes passes it over and runtimeProcess composes none for a held runtime (what runs of either is carried, as before). A module of its own account left without its runtime by a held runtime is refused with a typed NoRuntimeToRunError, which makes the held runtime the culprit, so those modules are held after it and the node composes the rest.Delivery
novox/mesh-sdk@eff81f1220e2— merged since 2026-10-30T21:17:41ZSource — source.main moved to novox/mesh-sdk@b74e23f973. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Group
fix/held-module-and-assigner-contract: novox/mesh-catalog@b5475cfa5c, novox/mesh-delivery@8fe6442c47, novox/mesh-host@62cfb45789, novox/mesh-sdk@eff81f1220Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.