The watchman states the lane floor instead of waiting for a change - #4474
Merged
Merged
Conversation
…r a change capacity-shrank needs two readings and fires only on a CHANGE, so a swarm that has been small since before the first reading is invisible to it. Across 2026-09-20 something outside both repositories rewrote TRIOS_QUEEN_MAX_WORKERS to 8, then 9, then 1, then 16, and every write redeployed the service. The image built that day derives the lane count and ignores that variable; an older image does not, and a redeploy can bring one back - which is exactly when the value bites. So the floor is stated rather than inferred: PUSHER_EXPECTED_LANES, default 20, being ten credentials at two lanes each. Below it the rule names both causes it can be - an older image, or a credential that stopped being counted - and points at the entrypoint line that tells them apart. Thirty rule shapes, twelve of them ones a moving system must NOT fire. Closes #4473 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
September 20, 2026 17:15
Contributor
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
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
2 participants
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.
Closes #4473
capacity-shrankfires only on a change between two readings. A swarm thathas been small since before the first reading is invisible to it.
Across 2026-09-20 something outside both repositories rewrote
TRIOS_QUEEN_MAX_WORKERSto 8, then 9, then 1, then 16 — four times — andevery write redeployed the service.
The image built that day ignores the variable:
An older image does not, and a redeploy can bring one back — which is exactly
when the value bites. That happened twice yesterday, both times within a minute
of a variable change I made myself.
So the floor is stated:
PUSHER_EXPECTED_LANES, default 20 — tencredentials at two lanes each. Below it the rule names both causes it can be and
points at the entrypoint line that tells them apart.
🤖 Generated with Claude Code