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.

This commit is contained in:

jschoubben

2026-10-25 18:53:04 +01:00

parent 2df0503034

commit 78d26867d2

21 changed files with 58 additions and 31 deletions

									
										modules/mesh-build-node/module.json
									
		+1
		-1
	
												View File
												
				@@ -10,7 +10,7 @@

				  "state": [

				    "toolchains",

				    "keys",

				    "steps"

				    {"name": "steps", "ttl-seconds": 172800}, "pauses"

				  ],

				  "claims": [

				    {