jschoubben 24c23a1d06 A module the node holds alone marks that module, keeps what runs of it, and never refuses the node (issue 1126) ...

frombus.Compose now holds a module refused alone (mesh-sdk 0de3006, the rule
its answer follows too): composed as what runs of it, with what depends on
how it is held held too. The composer hands every other module, keeps what it
handed of a held one, and tells the agent which modules it holds and why;
agent.NotComposedEach marks those alone and clears the rest. Only a refusal
of no single module still marks every module (NotComposed).

heldOut also holds out, of the node's own composition as it runs, the
resources of each module held alone, until a composition of its own is
handed: the node's own apply never removes a module leaving the fold with its
names unset (review of the apply, round 1; issue 1945 by a new path).

Pins mesh-sdk fix/1126-apply-culprit at 0de3006 (a group).

2026-10-28 17:23:26 +01:00

..

testdata

A module the node holds alone marks that module, keeps what runs of it, and never refuses the node (issue 1126)

2026-10-28 17:23:26 +01:00

selfcompose_test.go

A module the node holds alone marks that module, keeps what runs of it, and never refuses the node (issue 1126)

2026-10-28 17:23:26 +01:00

selfcompose.go

A module the node holds alone marks that module, keeps what runs of it, and never refuses the node (issue 1126)

2026-10-28 17:23:26 +01:00

shadow.go

Say which input woke each placement candidate's answer, so a probe's safety check tells a loop from moving inputs (issue 1126)

2026-10-28 14:44:27 +01:00