fix(community): improve TogetherAI error handling for chat models #8949
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
This PR fixes an issue where users attempting to use chat/instruct models with the
TogetherAI
class would encounter a cryptic error:Cannot read properties of undefined (reading 'choices')
. This happened because the TogetherAI API returns different response formats for text completion models vs chat models, and users were unknowingly using the wrong class.Changes Made:
Improved Error Handling: Added proper error handling in the
_call
method to catch when the API response doesn't match the expected format and provide a helpful error message directing users to useChatTogetherAI
instead.Model Type Detection: Implemented automatic detection of chat/instruct models (based on patterns like "instruct", "chat", "vision", or "turbo" in model names) and added a console warning when users instantiate
TogetherAI
with these models.Documentation Updates:
Tests: Added unit tests to verify the warning behavior and model type detection.
Example of the fix in action:
Before (confusing error):
After (helpful guidance):
This slightly improves the developer experience by providing clear guidance on which class to use for different model types.
Fixes #6993