-
Notifications
You must be signed in to change notification settings - Fork 60.8k
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
[Feature Request]腾讯云的deepseek R1,没有think过程的问题 #6197
Comments
请问腾讯接口怎么设置的啊 |
How to set up the Tencent interface? |
请问腾讯接口怎么设置的啊 |
How to set up the Tencent interface? |
关于上面问到腾讯接口怎么设置的,我的docker compose设置如下: |
打开控制台我发现思维链的内容存在websocket里面的ReasoningContent里面,应该修改一下代码就可以 |
Open the console and I found that the content of the thinking chain is in the ReasoningContent in the websocket. You should modify the code. |
同样的问题,用阿里百炼deepseek是有的,但是需要用网友上传的Nightly版本镜像,因为官方镜像已经很久没有更新了。 version: '3'
services:
nextchat:
image: rocky9/nextchat-nightly:latest
container_name: nextchat
restart: always
ports:
- "3000:3000"
environment:
- DEEPSEEK_URL=https://dashscope.aliyuncs.com/compatible-mode/v1
- DEEPSEEK_API_KEY=sk-xxx
- CODE=xxx
- CUSTOM_MODELS=+deepseek-r1@DeepSeek
- DEFAULT_MODEL=deepseek-r1@DeepSeek |
For the same problem, there is a deepseek application using Alibaba Bailian deepseek, but it needs to be mirrored using the Nightly version uploaded by netizens, because the official image has not been updated for a long time. version: '3'
services:
nextchat:
image: rocky9/nextchat-nightly:latest
container_name: nextchat
restart: always
Ports:
- "3000:3000"
environment:
- DEEPSEEK_URL=https://dashscope.aliyuncs.com/compatible-mode/v1
- DEEPSEEK_API_KEY=sk-xxx
- CODE=xxx
- CUSTOM_MODELS=+deepseek-r1@DeepSeek
- DEFAULT_MODEL=deepseek-r1@DeepSeek |
🥰 Feature Description
我部署的是docker镜像,目前最新的v2.15.8,用的是腾讯云提供的deepseek大模型R1,在使用时,我发现nextweb上不会显示think过程,而我直接调用腾讯云的api接口是有的。请问是目前版本还没针对腾讯云的deepseek做出think功能,还是我配置有问题呢?另外,我看到github上的图是有think功能的。
🧐 Proposed Solution
解决调用腾讯云的deepseek R1,没有think过程的问题
📝 Additional Information
No response
The text was updated successfully, but these errors were encountered: