fix(deepseek): handle array inputs #34228
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
github-actions
bot
added
integration
Author
ccurme
reviewed
Dec 12, 2025
Collaborator
ccurme
left a comment
ccurme
left a comment
There was a problem hiding this comment.
Can you clarify the issue here? All this is fixing is changing the string
"[]"
to the empty string "".
Does DeepSeek treat the string "[]" as an array?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 issue where Deepseek's ToolMessage field does not accept array input. Created workaround by converting array inputs into strings. Adjusted relevant test cases.
Files modified:
libs/partners/deepseek/langchain_deepseek/chatmodels.py
libs/partners/deepseek/tests/unit_tests/test_chat_models.py
Fixes #33965
Used Cursor for assistance