Skip to content

v0.11.1 — Fix per-call token guard

Choose a tag to compare

View all tags
@Rynaro Rynaro released this 15 Jun 13:26
· 52 commits to main since this release
v0.11.1
51f0a46
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Patch fix for a v0.11.0 regression.

After v0.11.0 began sending real diff content to the provider, non-trivial PRs failed with "capability: request exceeds maxTokensPerCall" before any provider call. The adapter pre-flight guard (maxTokensPerCall = MAX_TOKENS_PER_PR / 2 = 30k) sat below the chunker's per-call budget (chunking.call_token_budget = 60k), so the chunker built batches the adapter then rejected. Empty content hid the mismatch pre-v0.11.0.

Fix: the guard is a backstop, not the primary control — it must sit above the chunker budget plus serialization overhead. Removed the / 2 (maxTokensPerCall = MAX_TOKENS_PER_PR) and raised the MAX_TOKENS_PER_PR default to 120000. Regression test added; runbook updated.

No config change required — operators on the default pick this up automatically. If you raised chunking.call_token_budget above ~90k, also raise MAX_TOKENS_PER_PR to keep the guard above it.

736 tests · 15/15 eval scenarios · typecheck + lint clean.

Assets 2
Loading