Fix usage tracking for SiliconFlow etc #1558
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.
Context
As described in #1227, some APIs return the usage counts in every chunk, causing our current method of tracking to show completely inaccurate counts (and likely confusing the sliding window calculations).
Implementation
@tbphp had a great suggestion here to just use the last usage if there are multiple: #1227 (comment)
Screenshots
How to Test
I signed up for the SiliconFlow provider at https://siliconflow.cn/ and used the free
deepseek-ai/DeepSeek-R1-Distill-Qwen-7Bmodel to test.Important
Fixes usage tracking in
OpenAiHandlerby using only the last usage metrics from API streams, with comprehensive tests added.OpenAiHandlerby using only the last usage metrics from API streams.openai-usage-tracking.test.tsto test usage metrics handling with multiple chunks, final chunk only, and no usage data scenarios.createMessage()inopenai.tsto store and yield the last usage metrics.This description was created by
for f306461. It will automatically update as commits are pushed.