Keep a build node's pause in a state of its own, and pull as not paused when the pause cannot be read (steps bucket full, 2026-10-25)

+51 -12

2 Commits

Author	SHA1	Message	Date
jschoubben	518dae5ec9	Pull as not paused when the pause cannot be read, and say so once, instead of ending the puller silently mesh/delivery held for a person: merged without a passing check: only a person decides what follows Details mesh/delivery-group group fix/steps-bucket-ages held: a member is held: novox/mesh-sdk@518dae5ec9c8 (merged without a passing check: only a person decides what… Details mesh/check checking 518dae5ec9c8 on 7f89cb51de15 \| novox/mesh-sdk#81 in group fix/steps-bucket-ages A Load error ended Pull, and the modules run it in a goroutine whose error nobody reads: every build node would stop pulling when the new pauses state could not be read (or when Pull reached restore before Serve). A node kept from building is held by capacity 0, not by a pause.	2026-10-25 18:56:17 +01:00
jschoubben	e8f8ef63fa	Keep a build node's pause in a pauses state of its own, so the steps state can drop its old keys without ending a pause The steps state of the build modules filled to the bus's 64 MiB cap (27,370 keys of mesh-build-go, none ever removed) and refused a passed check's end. Its keys get an age in the catalogue; the pause key lived among them and would then have ended by itself. Puller.PausePut writes it to delivery.PausesState instead; Put stays the fallback for a module not yet moved.	2026-10-25 18:51:04 +01:00

Keep a build node's pause in a state of its own, and pull as not paused when the pause cannot be read (steps bucket full, 2026-10-25) #81