Build modules' steps live two days and their pause has a state of its own, so the steps bucket no longer fills (2026-10-25) #481

Merged

jschoubben merged 2 commits from fix/steps-bucket-ages into main 2026-10-25 18:06:40 +00:00

Conversation 1 Commits 2 Files Changed 24

+61 -31

2 Commits

Author	SHA1	Message	Date
jschoubben	4e82a824be	Announce the pauses state in the three build modules, and pin mesh-sdk 518dae5 (an unreadable pause pulls as not paused) ... Without it in Kept, stdio.KeptState refuses the state before the bus (mesh-sdk go/keeps.go refusedUnannounced), so the pause could be neither read nor written.	2026-10-25 18:57:08 +01:00
jschoubben	78d26867d2	Give the build modules' steps state an age of two days, and keep a node's pause in a pauses state of its own ... mesh-build-go's steps bucket filled to the bus's 64 MiB cap (27,370 keys, none ever removed) and refused the end of a passed check, so the check read failed; mesh-build-node's (17.8 MB) and mesh-build-image's grow the same way. A step's key is per step: its reader reads its end within the step's bound, and a check's verdict is kept by the checker, so two days is ample. The node's pause key lived in the same bucket and would have ended by itself; it moves to a pauses state without an age (mesh-sdk fix/steps-bucket-ages, Puller.PausePut). No node is paused today, so nothing is carried over.	2026-10-25 18:53:04 +01:00