Handle structured token usage details#1680
Open
AgenticSpark wants to merge 1 commit into
Open
Conversation
Flatten numeric fields from OpenAI SDK usage detail objects before summing token usage, so final reporting no longer raises when completion_tokens_details is present. Tested with: uv run --no-project --with pytest --with blobfile --with openai --with tiktoken --with pyyaml --with pandas --with numpy --with snowflake-connector-python --with beartype --with requests --with filelock --with tqdm --with typing-extensions --with lz4 --with zstandard --with backoff pytest evals\\cli\\oaieval_test.py -q Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
AgenticSpark
requested review from
andrew-openai,
etr2460 and
katyhshi
as code owners
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.
Fixes #1582.
Token usage aggregation now converts OpenAI SDK usage objects into mappings and only sums numeric fields. Numeric nested detail fields such as
completion_tokens_details.reasoning_tokensare included under flattenedusage_*result keys, so final reporting no longer raises when structured usage details are present.Tested with:
uv run --no-project --with pytest --with blobfile --with openai --with tiktoken --with pyyaml --with pandas --with numpy --with snowflake-connector-python --with beartype --with requests --with filelock --with tqdm --with typing-extensions --with lz4 --with zstandard --with backoff pytest evals\\cli\\oaieval_test.py -q