{{ message }}
Repository navigation
fix(count-tokens): retry after transient counting failures - #34
Merged
faj-design5260 merged 1 commit intoOct 28, 2026
Merged
faj-design5260 merged 1 commit into
faj-design5260 merged 1 commit into
Conversation
rudycelekli
marked this pull request as ready for review
October 9, 2026 22:45
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.

Unavailable count-token responses are cached indefinitely as None. Cache successful results only so a later analysis can recover after a transient service failure.
Validation: the added regression fails on upstream 069733f and passes on this branch. The complete isolated suite passes (225 passed, 2 skipped in 9.82s); Ruff 0.16.10 and git diff --check pass.
Python3.13/macOS with isolated credential/config fixtures, real installed dependencies and Ruff0.16.10. No live provider calls; hosted Python3.10/3.11/3.12 not yet verified.