Wake a parked build puller when its capacity changes, so a node raised from capacity 0 takes asks (issue 1887) #80

Merged

jschoubben merged 3 commits from fix/puller-wakes-on-capacity into main 2026-10-25 17:10:34 +00:00

Conversation 1 Commits 3 Files Changed 7

+241 -31

3 Commits

Author	SHA1	Message	Date
jschoubben	a8fbabbfc3	Fold the puller-wake and Served tests into existing tests to stay within the test budget (issue 1887)	2026-10-25 17:44:03 +01:00
jschoubben	b9911dc1c1	Start the puller's capacity watch once Serve has the runtime's channel, since a build module pulls before it serves (issue 1887) ... A watch asked before Serve is refused, which would have left every build module on its settings file again. stdio.Served closes when Serve has the channel; WatchConfigServed waits on it, and Pull starts the watch beside its loop.	2026-10-25 17:26:10 +01:00
jschoubben	e6b2df6506	Wake a parked build puller on its capacity's own change, so a node started at capacity 0 takes asks once raised (issue 1887) ... g14's Go builder sat idle at capacity 2 while delivery builds waited: a puller with no room waited on its wake alone, which only a pause, a resume or a step's end gives, and it read its capacity from the settings file only when woken. The puller now follows the module's config value capacity through the runtime's watch of what mesh-config resolved (stdio.WatchConfig), uses the value it hands, and wakes on each change: no timer, no file watch, and no wait for the node-engine to fill the file again. It says when it parks and when it wakes, with its capacity.	2026-10-25 17:23:28 +01:00