Repository navigation
feat(runner): hot apply Job capacity through fenced config reload - #1325
Merged
Merged
Conversation
This was referenced Oct 27, 2026
yyjeqhc
force-pushed
the
feat/runner-capacity-hot-reload
branch
from
October 27, 2026 12:02
23205c2 to
61e5b76
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changing
max_concurrent_jobsnow applies through the existing Check → Reload transaction and Unix SIGHUP. Growth immediately schedules the original queue; shrink keeps running Jobs intact and waits for occupied slots to fall below the new limit. Desktop stages, checks and hot-applies the same setting without restarting.Stacked on #1324. Merge B first, then retarget this PR to main. Independent Trace PR: #1326. No automatic merge or deployment.
Ownership and activation
Validation on mini, using isolated fixtures
Stream metadata following SIGHUP converges on the existing keepalive cadence; formal tool reload also triggers metadata submission. Legacy Servers cannot live-update the new capacity field. QUIC uses the existing isolated TLS integration harness, while the standalone reload script covers Polling and WebSocket. No production configuration edits, service restarts or deployment were performed.
Final CI for
23205c253: every selected check passed, including Linux Server/Runner/workspace/tooling, macOS core/Desktop, Windows core/Runner/Desktop, contract, MCP conformance and aggregate gates. Docker Server and the separate Windows package job were skipped by the workflow matrix. Workflow: https://github.com/yyjeqhc/webcodex/actions/runs/40493574239 .