Non-oai usage meta + non-oai client types #182
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.
fix client inference for non oai + check for usage for non-oai and non-readable
We were not passing through usage into meta for llm-polyglot/anthropic clients because the existing logic to do it checked explicitly for OAI clients + dependent on the response being a stream that could be .tee'd
This update does a similar "tee" for the iterable so we can read in parallel but doesn't have the same stream_options check so it will always run for any non-oai clients - if they don't provide usage it will just ignore.
Additionally, client inference has been updated slightly to get rid of the annoying non oai client type errors