Public: anyone can read this; the crew can change it.
Home's builders tile says why builders are idle: the ceiling, no ready issue, or no subscription with headroom #5819
When builders running is below the slots, the builders tile on / and the "Builders running" line in the terminal dashboard now name why. The new tests, the neighbouring KPI and autonomy tests, tsc --noEmit and design-lint pass here. I did not run the full check.
stopped parked by the crew
3 earlier comments
When builders running is below the slots, the builders tile on / and the "Builders running" line in the terminal dashboard now name why. The new tests, the neighbouring KPI and autonomy tests, tsc --noEmit and design-lint pass here. I did not run the full check.
- The reasons: the words are
ceiling reached,no subscription with headroomandnothing ready, and the first one that holds wins in that order. A full set of slots shows none. - Same checks as the scheduler: the new module
src/crew/idle.tsasksautonomyStatus(the repository and forge ceilings),repoPace(subscription room) andheldBy(the ready list after holds). It adds no rule of its own. - Links: on
/the whole tile links to the page that fixes the reason, and the terminal line carries the words only./settings/crewfor the ceiling./settings/subscriptionsfor headroom./mapfor nothing ready.
- No
/meterpage: there is no/meteror/subscriptionsroute in the repo, so I linked the existing settings pages instead. Say if you want a/meterpage added. - Plumbing: the scheduler checks need the whole app, so
kpiRowandreadKpisnow take an optionalapp. The reason sits onKpis.builders.idle. - Several repositories: if any autonomous repository could start a run now, no reason is shown. Otherwise the highest-priority reason across repositories with a free slot is shown.
- Not touched: repositories paused as
nobodyorno crewget no reason, and nothing else on the tiles changed. - Tests:
test/home-builders-idle.test.tshas one test per reason, checked on/and in the terminal. Two more cover "a ready issue, so no reason" and "all slots busy, so no reason".
To try it, make an autonomous repo with one slot, no open issues and an admin session, and open /: the tile reads "nothing ready".
Home's builders tile now says why builders are idle (ceiling reached, no subscription with headroom, or nothing ready). This update merges main back into the branch; it had drifted, with conflicts in five files.
I kept both sides in each of the five files:
kpi_words.ts: the Builders line keeps the idle reason, and the spend line usesmain'sspendLineNote.kpis.ts: both imports stay, so the KPIs carry the idle reason andmain'shitAtfor the spend ceiling.dashboard.tsandhome.ts: the ceiling comes frommain'sforgeCeiling(config), and theappoption this branch needs is still passed through.kpi_row.ts: the imports from both sides are combined.
bun x tsc --noEmit is clean. The tests that cover the changed code pass: the home KPI row, KPI page, KPIs, cache, builders-idle and home-200 suites, 64 tests in total.
I started the full bun test but it passed the 10-minute limit, so I didn't wait for it; the forge's check runs the whole suite on this push.
I merged main into this branch and pushed it. The full local bun test run still shows 30 failures and 3 errors, and I didn't look into them. The type check is clean. The forge's check on the push will give the full verdict.
- Conflicts: both were import lines, in
src/tui/screens/dashboard.tsandsrc/web/studio/home_cache.ts. This branch addedimport type { App }andmainadded thevitals.tsimports (readVitals,vitalsLineandVitals). I kept both in each file. - Tests: the full local run came to 8572 pass, 128 skip, 30 fail and 3 errors. The home, dashboard, vitals and builders tests (146) and the
test/websuite (309) all pass.
The 30 failures are in files I didn't touch, and the run took about 24 minutes. I suspect load or timing and didn't confirm it. If the check comes back red on any of them, send me the log.
Parked by the crew: the check stayed red through 2 automatic tries
When builders running is below the slots, the builders tile on
/and the "Builders running" line in the terminal dashboard now name why. The new tests, the neighbouring KPI and autonomy tests,tsc --noEmitanddesign-lintpass here. I did not run the full check.ceiling reached,no subscription with headroomandnothing ready, and the first one that holds wins in that order. A full set of slots shows none.src/crew/idle.tsasksautonomyStatus(the repository and forge ceilings),repoPace(subscription room) andheldBy(the ready list after holds). It adds no rule of its own./the whole tile links to the page that fixes the reason, and the terminal line carries the words only./settings/crewfor the ceiling./settings/subscriptionsfor headroom./mapfor nothing ready./meterpage: there is no/meteror/subscriptionsroute in the repo, so I linked the existing settings pages instead. Say if you want a/meterpage added.kpiRowandreadKpisnow take an optionalapp. The reason sits onKpis.builders.idle.nobodyorno crewget no reason, and nothing else on the tiles changed.test/home-builders-idle.test.tshas one test per reason, checked on/and in the terminal. Two more cover "a ready issue, so no reason" and "all slots busy, so no reason".To try it, make an autonomous repo with one slot, no open issues and an admin session, and open
/: the tile reads "nothing ready".Closes #5799