Print max_live_claims on the buffer shape line (T-339) - #238
Open
chasers wants to merge 1 commit into
Open
Conversation
The knob decides how many storage slots one ref's backlog can occupy, and the shape line is how a pushed setting is confirmed after an ESO sync — the T-330 roll showed a hand-set override can outrank the Secret through two rollouts, so a knob that is not on the line is a knob nobody can verify took. It sits beside the claim valves it works with. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
max_live_claimsdecides how many storage slots one ref can occupy, but was missing from thebuffer shape:boot line — the tool for confirming a pushed setting actually took after an ESO syncStacked on #236; merge that first and this retargets.
🤖 Generated with Claude Code