-
-
Notifications
You must be signed in to change notification settings - Fork 11.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weโll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Lobe does not support deep thinking feature for ollama deepseek r1 models #5591
Comments
๐ @ShinChven Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
The issue you're experiencing with the For the padding issue at the top of the message box, the padding is defined in the To resolve the issue with the 'deep thinking' feature, you may need to check the integration logic for the Ollama DeepSeek R1 model and ensure it aligns with how the feature is triggered for the official DeepSeek API. This might involve reviewing the configuration files or settings that define how different AI models and their features are integrated into Lobe, which are located in the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
โ @ShinChven This issue is closed, If you have any questions, you can comment and reply. |
๐ This issue has been resolved in version 1.49.8 ๐ The release is available on: Your semantic-release bot ๐ฆ๐ |
๐ฆ Environment
Docker
๐ Version
v1.48.0
๐ป Operating System
macOS
๐ Browser
Chrome
๐ Bug Description
When running deepseek-r1:8b via Ollama, Lobe displays the <think> tag in text instead of prompting the
deep thinking
feature as it did when calling the official DeepSeek API. Additionally, there is a padding issue at the top of the message box when displaying the <think> tag, see it in the screenshot.๐ท Recurrence Steps
No response
๐ฆ Expected Behavior
No response
๐ Additional Information
No response
The text was updated successfully, but these errors were encountered: