fix(openai): usage parsing for streamed responses #1184
Merged
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.
Important
Adds
usage_details
key to_create_langfuse_update()
inlangfuse/openai.py
for detailed usage data.langfuse/openai.py
,_create_langfuse_update()
now addsusage_details
key with parsed usage data, in addition tousage
key.This description was created by
for 1743c97. You can customize this summary. It will automatically update as commits are pushed.
Greptile Summary
Disclaimer: Experimental PR review
Updates OpenAI integration to fix usage parsing for streamed responses, ensuring consistent token tracking across different response types and maintaining backward compatibility.
langfuse/openai.py
to store usage data in both 'usage' and 'usage_details' fields for backward compatibilityOpenAiCompletionUsageSchema
andOpenAiResponseUsageSchema
_create_langfuse_update
function to handle streamed responses correctly