bvandeusenandClaude Opus 5
1353d346b3
CI and images / lint (push) Successful in 3s
CI and images / extension-version (push) Successful in 3s
CI and images / frontend-build (push) Successful in 25s
CI and images / backend-lint-and-test (push) Successful in 33s
CI and images / integration (push) Successful in 2m13s
CI and images / sign-extension (push) Successful in 3s
CI and images / build-agent (push) Successful in 6s
CI and images / build-web (push) Successful in 1m59s
CI and images / smoke-web (push) Successful in 58s
CI and images / promote (push) Skipped
Operator: "when the number is changed the change should be queued so that
it isn't blocking of the webui or the system itself. we shouldn't have to
wait for the validation live."
Two waits, and 5b6f2ba removed neither — it stopped a Postgres connection
being HELD across them, which is what had been stalling the whole site,
and left the press itself as slow as it was.
1. The store refetched after every write. GET /api/system/workers runs a
celery inspect on an eleven-second budget, so the stepper stayed
disabled through a round trip the press did not need. It now patches
the row from the reply — cap, ceiling, enabled, the three fields that
reply actually decides — and lets the 15s poll bring the live columns,
which are measurements it must not invent.
2. The endpoint pushed to the broker before answering. Turning a lane off
is four cancel_consumer messages; lowering a cap reads the live pool
first. Now it stores the cap, answers `queued`, and hands the push to a
Quart background task. Raising a cap was already free and stays free.
Nothing is lost by not waiting: the stored cap is what the system obeys
and the sizing pass re-reads it every minute. That sweep was already the
backstop for a push that failed, which under `no_live_workers` is every
push in the suite.
Also closes a hole the move exposed: the model fetch was gated on the
consumer change having landed, so raising ML off zero while the lane was
restarting stored the cap, let the sizing pass start the consumers a
minute later, and left the lane running with no model — nothing else ever
asks for one. It now fires on the transition and waits in the ml queue.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LVjrnpQjRgHdvq95rASoiR