5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	c47afd8f4b	build_usage says a seat's build hours, and when it is outside them ... A build module's capacity.<node> now carries its node's build window (the operator, 2026-10-26: g14 builds only from 18:00 to 06:00); the seat shows it, outside it says it takes nothing new, and a value the module cannot read shows as any hour with the value and why. The checker's and the view's SDK pin moves to mesh-sdk d00dac1.	2026-10-26 21:22:36 +01:00
jschoubben	6d60953f98	A running try names its asks and where each stands; build_usage says a seat's CPU-bound capacity ... The checker wrote a try's asks only at its end, so a 31-minute try could not be told queued from running (issue 1890). The try's record now names each ask as it is put, then the node that took it, its state and the phase its step says, written on the step key's own changes. build_usage names a running try's asks and takes a build module's capacity.<node> (configured bounded by its node's build CPU, issue 1806's follow-up) when it is current with mesh-config.	2026-10-26 19:58:39 +01:00
jschoubben	4f722899df	View: build_usage does not answer eligibility it cannot read; a resolved capacity key with no readable value is the puller's 0 ... A capacity this tool cannot read is unknown to it, not 0: the seat says eligible_known false and the node not known. A key mesh-config holds without a readable value is what the puller reads as 0, and was dropped silently.	2026-10-26 14:58:47 +01:00
jschoubben	166a918b43	View: build_usage counts keys a build module ended for being left running apart, lists every node a capacity names, and says capacity unknown when mesh-config cannot be read ... Since mesh-sdk #90 a build module ends a left-running key as failed at the moment it notices; counted as finished, such a step put hours into the medians and the time at capacity. The view takes mesh-sdk's step bound and restart reason from the SDK it now pins.	2026-10-26 14:58:47 +01:00
jschoubben	3b6945b2db	View: build_usage answers how the build nodes are used in one call; the checker's tries name their asks ... The operator's question (how much are the build nodes used, is ace eligible) took six calls over four tools. build_usage reads it from the bus's states: seats held (have), capacity (mesh-config resolved), pauses, the build modules' steps by kind with left-running keys, the last hour and day with total and median time and time at capacity, the running tries, and the backlog the view program reads from the seats' streams. A try now names the asks it put, and the checker announces its tries readable, so the view tells a try's asks from a check's.	2026-10-26 14:58:41 +01:00