-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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] 插件多轮调用报错 #4786
Comments
👀 @cookieY Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
I found a similar discussion that might be relevant to your issue. In the thread titled "[Q&A] 使用 coplilot-gpt4-service 时,调用插件没有后续对话?" on the Lobe Chat repository, it was mentioned that the copilot-gpt4-service does not support function calls, which could be related to the issue you're experiencing with plugin calls in server deployment mode [1]. If your issue is related to the OpenAI plugin system in Lobe Chat version v1.33.0, there might be specific configurations or limitations affecting the multi-round plugin calls. Unfortunately, I couldn't find specific known issues or limitations documented for this version regarding the OpenAI plugin system. However, ensuring that your configuration settings, such as API keys and endpoints, are correctly set up might help resolve the issue [2][3]. If the problem persists, reviewing the error messages or codes returned during the plugin call failures could provide more insight into the underlying issue [4][5][6][7]. |
应该是个 bug,晚上修下 |
It's probably a bug, I'll fix it tonight |
✅ @cookieY This issue is closed, If you have any questions, you can comment and reply. |
🎉 This issue has been resolved in version 1.33.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
📦 部署环境
Docker
📌 软件版本
v1.33.0
💻 系统环境
macOS
🌐 浏览器
Chrome
🐛 问题描述
服务端部署 模式使用 openai 进行多轮对话并使用插件的场景下,除第一次调用插件成功外,后续均会报以下错误
以下是请求值
客户端直连 模式下没有这个情况
📷 复现步骤
No response
🚦 期望结果
支持插件多轮调用
📝 补充信息
No response
The text was updated successfully, but these errors were encountered: