frombus: blame only the modules a refusal names, and say which providers another node cannot run (issue 1126, group fix/1126-shadow-bodies) #113

Merged

mesh-tools merged 1 commits from fix/1126-shadow-bodies into main 2026-10-28 07:46:24 +00:00

Conversation 2 Commits 1 Files Changed 6

+64 -9

mesh-tools commented 2026-10-28 00:45:47 +00:00

Member

Copy Link

Copy Source

Delivery group fix/1126-shadow-bodies with mesh-host and mesh-delivery.

• The search for the module to blame tries only modules the refusal names, at most 8; a refusal naming none is answered at once (ace took 7m46s composing the whole mesh once per placed module).
• A refusal names each module another node cannot run and what it lacks, and each node left out (K1: providers on novox vanished from ace's and g14's compositions; the next probe shows why).

Tests: rows in answer_rows_test, each failing without its fix.

Reviewed-by: review-bodies@shanks at 362a3f1378

Delivery group fix/1126-shadow-bodies with mesh-host and mesh-delivery. - The search for the module to blame tries only modules the refusal names, at most 8; a refusal naming none is answered at once (ace took 7m46s composing the whole mesh once per placed module). - A refusal names each module another node cannot run and what it lacks, and each node left out (K1: providers on novox vanished from ace's and g14's compositions; the next probe shows why). Tests: rows in answer_rows_test, each failing without its fix. Reviewed-by: review-bodies@shanks at 362a3f1378aace745b81b712e24f198f62c01ef5

mesh-tools added 1 commit 2026-10-28 00:45:48 +00:00

A refusal for want of a provider names the modules another node cannot run in this composition, and a refusal naming no placed module is answered at once (issue 1126, probe #532) ... 362a3f1378

ace and g14 answered 'nothing in this mesh provides artifact-store … assign
distribution to a node' while novox runs it: a module another node cannot run
in this composition (catalogue Resolution.Unhostable) offers nothing, silently.
The refusal now names each such module and what it lacks, and each node left
out. And the culprit search composed the whole mesh once per placed module for a
refusal no stub changes (ace's answer took 7m46s): only the modules the refusal
names are tried, at most 8.

mesh-tools commented 2026-10-28 00:45:52 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-sdk@362a3f1378aa — merged since 2026-10-28T07:46:26Z

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

Group fix/1126-shadow-bodies: novox/mesh-delivery@289d1e8fa6, novox/mesh-host@82d0e125b2, novox/mesh-sdk@362a3f1378

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

Transitions

• 2026-10-28 00:45 (new) → proposed (announced): novox/mesh-sdk#113's head announced
• 2026-10-28 00:45 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-28 07:46 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@362a3f1378aa` — **merged** since 2026-10-28T07:46:26Z **Source** — source.main moved to novox/mesh-sdk@be77f6656326. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `fix/1126-shadow-bodies`: novox/mesh-delivery@289d1e8fa69a, novox/mesh-host@82d0e125b2c0, novox/mesh-sdk@362a3f1378aa - composed together: pass — the checker's verdict at the members' heads (409daa55f579) **Transitions** - 2026-10-28 00:45 (new) → proposed (announced): novox/mesh-sdk#113's head announced - 2026-10-28 00:45 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-28 07:46 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 commented 2026-10-28 00:50:02 +00:00

Author

Member

Copy Link

Copy Source

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-tools merged commit be77f66563 into main 2026-10-28 07:46:24 +00:00

mesh-tools deleted branch fix/1126-shadow-bodies 2026-10-28 07:46:24 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-sdk#113