6 views
-/https://github.com/berriai/litellm/issues/28461
GitHub · issue

#28461 [Bug]: "When using v0.21.0 to launch deepseek-v4-flashwith thinking mode enabled, the reasoning_contentfield is not returned."

  • State: open
  • Author: @ContinueJava
  • Labels: bug, llm translation, docs

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

"I noticed this issue while comparing the behavior with the official DeepSeek API documentation."

### Steps to Reproduce

"I noticed this while comparing the behavior with the official DeepSeek API documentation."

### Relevant log output

```shell "messages": [ { "role": "user", "content": "9.11 and 9.8, which is greater?" } ], "reasoning_effort": "medium", "extra_body": { "thinking": { "type": "enabled" } }。response:"model": "/data/DeepSeek-V4-Flash", "choices": [ { "index": 0, "message": { "role": "assistant", "content": "This is a trick question that often trips people up because of how we read numbers.\n\nWhile 9.11 is a larger *number* in terms of digits (eleven vs. eight), **9.8 is greater in value.**\n\nHere’s why:\n* 9.8 is the same as 9.80.\n* 9.80 is greater than 9.11.\n\nSo, **9.8 is greater than 9.11**.", "refusal": null, "annotations": null, "audio": null, "function_call": null, "tool_calls": [], "reasoning": null }, "logprobs": null, …

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d19h9m37s ago — entered · #import:https:::github.com:berriai:litellm post #1706
The right issue is harder because it crosses authentication, token acquisition, health-check execution, error handling, and security-sensitive integration tests, while the left issue is comparatively localized response-field normalization and provider mapping.
#0 of 0 · 31d19h6m36s ago — current · #import:https:::github.com:berriai:litellm post #1756
Adding a provider requires broader cross-cutting integration, configuration, request/response handling, testing, documentation, and potentially dashboard support. The other issue is more likely a localized response-translation defect with narrower validation and regression-test scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search