Skip to content

Capacity on conditions and caps, two tutorials, and fixes to runs and evidence - #726

Merged
GrahamDumpleton merged 14 commits into
developfrom
overlay-cap-tutorials-run-fixes
Nov 16, 2026
Merged

GrahamDumpleton merged 14 commits into
developfrom
overlay-cap-tutorials-run-fixes

Conversation

@GrahamDumpleton

@GrahamDumpleton GrahamDumpleton commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

What this changes

Seven issues from the board, one commit each, with eight problems found on the way, each filed and fixed here in a commit of its own.

Design choices

#712 (ADR 0065; specification 7.5 "Caps", 9.10 and 19.1):

  • Floor against cap: the cap wins over every floor: a schedule's, an overlay's, the policy's min_workers and a static count. muructl apply warns of a declared floor above another overlay's or schedule's cap on the same group. One overlay refuses a cap below its own floor, or beside max_workers.
  • Getting under a cap: the excess drains at once, as one decision, and the churn budget does not count it. --cap waits until the serving release's group is at or under the cap; --no-wait returns at once.
  • Overlay name: APP:cap (APP:cap:GROUP), apart from the floor's APP:scale, so each ends on its own.
  • Also settled:
    • A pin stands over a cap, as it does over a floor and the budget; --cap says so rather than waiting.
    • An advisory group reports the drain without acting.
    • A canary takes its share of the cap, rounded up and at least 1.
    • A warm-up's lead applies floors but not the cap.
    • cap_workers is a schedule key too.
    • Once a cap ends, a group under its floor or static count is raised back in batches of max_step_up.

#714: reach the newest run, with a note naming the others and their --socket, as suggested (specification 13.8).

#715: this departs in part from the suggested approach of the edge's in-flight list alone. The host asks a condemned worker to give up its requests before the kill, and the edge answers them at once, so by the time the kill event arrives the edge no longer lists them. That is exactly the GIL-held case in the issue. The worker's answer to that request names them without the interpreter, so it is the main source. The edge's list is kept for a worker stopped whole, which can answer nothing. Recorded in specification 11.7, "Captures".

#723: parents(false) alone would drop a monorepo's root rules. Instead, a watched directory that the enclosing repository ignores as a whole, and that is not a repository of its own, is walked by its own ignore files alone, as git would treat it as a repository (specification 9.8).

Checks

Closes #711
Closes #712
Closes #713
Closes #714
Closes #715
Closes #717
Closes #723
Closes #724
Closes #725
Closes #727
Closes #728
Closes #729
Closes #730
Closes #731

🤖 Generated with Claude Code

…older one though the newer says they reach it (#714)
@GrahamDumpleton
GrahamDumpleton marked this pull request as ready for review November 16, 2026 05:50
@GrahamDumpleton
GrahamDumpleton merged commit 7125a94 into develop Nov 16, 2026
25 checks passed
@GrahamDumpleton
GrahamDumpleton deleted the overlay-cap-tutorials-run-fixes branch November 16, 2026 06:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment