A module's bus account not issued yet is foreseen in a node's answer, so a new module can be assigned; a refusal leads with each held module's first reason (issue 774) #141

Merged
mesh-tools merged 2 commits from fix/kept-read-and-foreseen-account into main 2026-10-30 19:49:13 +00:00
Member

The assignment proposal of mesh-conditions, mesh-healers (novox) and mesh-self-check (ace) was refused at 20:24 with "has no bus credential: nothing was issued": an account can exist only after the Approve (ADR 0561 §1, ADR 0567 §5, ADR 0547 §9), so no new module with its own bus account could ever be assigned. 0cdbdca: in Foreseeing the account is foreseen; Reading still leaves out what was never issued, so no placeholder is sealed (issue 203 holds). 4e9621e: a refusal with no culprit leads with each held module's first reason, so a stand-in's later error never hides it.

Please wait for mesh/check to pass before merging; merge mesh-sdk first.

Reviewed-by: rev-sweep@shanks at 4e9621edd6

The assignment proposal of mesh-conditions, mesh-healers (novox) and mesh-self-check (ace) was refused at 20:24 with "has no bus credential: nothing was issued": an account can exist only after the Approve (ADR 0561 §1, ADR 0567 §5, ADR 0547 §9), so no new module with its own bus account could ever be assigned. 0cdbdca: in Foreseeing the account is foreseen; Reading still leaves out what was never issued, so no placeholder is sealed (issue 203 holds). 4e9621e: a refusal with no culprit leads with each held module's first reason, so a stand-in's later error never hides it. Please wait for mesh/check to pass before merging; merge mesh-sdk first. Reviewed-by: rev-sweep@shanks at 4e9621edd664a8150c495596484ef8e15bdd787b
mesh-tools added 2 commits 2026-10-30 19:37:21 +00:00
On 2026-10-30 the placement proposal p-20261030t192428-77dabc was refused on ace and novox: "has no bus credential:
nothing was issued for novox.mesh-conditions" (and mesh-self-check, mesh-healers). The vault mints a bus account from
the grants part's wanted list once the placement is written on the operator's Approve (ADR 0561 §1: "From the lease
write, the vault mints every new bus account and the controller mints none"; ADR 0567 §5: "A placement is written on
the operator's Approve"), so a shadow composition can never hold it, and no new module with its own account could be
placed.

Quick fix: skip the check for the three modules. Thorough fix: the Foreseeing mode foresees an unissued bus account like
any own secret the next step makes; the issue-203 refusal (busCredentialIssued), the controller's send's, is gone, and
the Reading mode still leaves out what was never issued. Chose thorough: it holds for every module with its own account.
Lead a refusal of a held module's stand-in with why the module was held, so its first reason is never hidden (issue 774)
mesh/delivery merged: source.main moved to novox/mesh-sdk@6a71d29b3331
mesh/delivery-group group fix/kept-read-and-foreseen-account merged: every member is merged
mesh/check pass 4e9621edd664 on 14de8dadb4ce | unit 2719 run, 602 kept, 36 skipped | integration 2731 run, 645 kept, 29 skipped | over bound: unit, in…
4e9621edd6
The proposal on ace said only "mesh-self-check runs as its own account and declares no own secret broker": the words
of its bare stub, held for "has no bus credential", which no one saw. The second hidden first reason of the day, after
"0 bundle(s)".

Quick fix: log the held map in composeEach. Thorough fix: firstReason leads a refusal no culprit is found for with the
first reason of every held module it names ("<m> is held: <why>; its stand-in is then refused: <err>"), for Compose and
the node's Answer alike; the hold's own why already keeps its first words. Chose thorough.
Author
Member

Delivery novox/mesh-sdk@4e9621edd664 — merged since 2026-10-30T19:49:16Z

Source — source.main moved to novox/mesh-sdk@6a71d29b33. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Group fix/kept-read-and-foreseen-account: novox/mesh-host@15361c661f, novox/mesh-sdk@4e9621edd6

  • composed together: pass — the checker's verdict at the members' heads (b768acf00ada)

Transitions

  • 2026-10-30 19:37 (new) → proposed (announced): novox/mesh-sdk#141's head announced
  • 2026-10-30 19:37 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 19:49 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@4e9621edd664` — **merged** since 2026-10-30T19:49:16Z **Source** — source.main moved to novox/mesh-sdk@6a71d29b3331. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `fix/kept-read-and-foreseen-account`: novox/mesh-host@15361c661f51, novox/mesh-sdk@4e9621edd664 - composed together: pass — the checker's verdict at the members' heads (b768acf00ada) **Transitions** - 2026-10-30 19:37 (new) → proposed (announced): novox/mesh-sdk#141's head announced - 2026-10-30 19:37 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 19:49 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-tools merged commit 6a71d29b33 into main 2026-10-30 19:49:13 +00:00
mesh-tools deleted branch fix/kept-read-and-foreseen-account 2026-10-30 19:49:13 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-sdk#141