mesh-build-node consumes the seat list's events, so its runtime's consumer exists
Its runtime follows the seat list (seatlist.Start subscribes to mesh-catalog.seat-definition-changed and -removed); with no consumes there was no consumer shanks_mesh-build-node_tools, the seat list was never read and the asks of a named asker were given back. Builds: design 47 G A-488a (hq 25df48ad) Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
@@ -277,6 +277,14 @@ func TestTheModuleRequiresNodeToolsItPullsThrough(t *testing.T) {
|
||||
if !slices.Contains(m.Requires, "node-tools") {
|
||||
t.Errorf("requires %v lack node-tools", m.Requires)
|
||||
}
|
||||
// Design 47 G A-488a: its runtime follows the seat list (seatlist.Start subscribes to the seat mesh-catalog's events), so the
|
||||
// module consumes both, which makes its durable consumer <node>_mesh-build-node_tools: with none, the seat list is never
|
||||
// read and the asks of a named asker are given back for ever.
|
||||
for _, ev := range []string{"mesh-catalog.seat-definition-changed", "mesh-catalog.seat-definition-removed"} {
|
||||
if !slices.Contains(m.Consumes, ev) {
|
||||
t.Errorf("consumes %v lack %s", m.Consumes, ev)
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
// Design 47 G A-254, A-313, A-314: the module keeps a run's answer over what step-ended carries inline in the steps state's own
|
||||
|
||||
Reference in New Issue
Block a user