Fix #2155 DeepSeek reasoning content handling for LiteLLM #2156
+101
−2
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
seratch
changed the title
Member
|
Thanks for sending this PR! One thing I want to check is that if this customization could be done on the LiteLLM side, that'd be the most appropriate situation for us. Have you considered contributing to the LiteLLM project? |
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.
Propagate
reasoning_contentonto assistant tool-call messages when using DeepSeek/thinking mode via LiteLLM. Extend the chat completion converter to optionally include reasoning content and enable it for DeepSeek. Added regression test covering reasoning content attachment.Fix LiteLLM DeepSeek thinking mode fails with missing
reasoning_contenon tool calls #2155make formatmake lintmake mypymake tests