fix(genai): include audio usage token details#1864
Open
vismaytiwari wants to merge 1 commit into
Open
Conversation
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.
Description
Fixes #1821.
This maps audio token counts from Google GenAI usage metadata into LangChain usage metadata. The response converter already reads aggregate token counts, but it ignored
prompt_tokens_detailsandcandidates_tokens_details, so TTS/audio responses lost theiraudiotoken breakdown.Relevant issues
Fixes #1821
Type
🐛 Bug Fix
Changes(optional)
input_token_details.audioandoutput_token_details.audiowhen present.GenerateContentResponse.Testing(optional)
uv run pytest tests/unit_tests/test_chat_models.py::test_response_to_result_includes_audio_usage_metadatauv run pytest tests/unit_tests/test_chat_models.py -k audiomake testfromlibs/genaimake lintfromlibs/genaiNote(optional)
I used Codex to help inspect the issue, implement the targeted change, and run the local validation commands. I reviewed the resulting diff before opening this PR.