mesh-sdk

Files

T

jschoubben d539d7e4eb Take the runtime as a culprit only where its stub composes, so node-tools is never held for an error that names it (issue 774)

The culprit rule held a module whose stub made the composition fail otherwise. The runtime's stub carries no bundle,
so it always fails otherwise: any refusal naming node-tools (or a module whose name holds it) held the runtime, and
the node was then refused whole for the runtime's "0 bundle(s)".

Quick fix: never take node-tools as a culprit. Thorough fix: blames, the rule as one function, takes the runtime only
where its stub composes. Chose thorough: a runtime whose stub composes may still be held alone.

2026-10-30 19:44:08 +01:00

frombustest

Hold only the module whose manifest the mesh refuses, so one bad item no longer fails every node's composition (issue 774)

2026-10-30 19:24:15 +01:00

testdata

A module's own refusal refuses that module, not the node: a stub whose contributions still fail the same is tried bare (issue 1126, seed-8: novox refused the whole candidate for de-spiegel's unset route names)

2026-10-28 14:07:59 +01:00

answer_rows_test.go

Never hold a module because a module it reads from is held: it composes with what the held one last offered (issue 1960)

2026-10-29 15:54:21 +01:00

answer.go

Take the runtime as a culprit only where its stub composes, so node-tools is never held for an error that names it (issue 774)