-
-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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] github 服务商配置不正常 #5354
Comments
👀 @git268 Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
我也发现这个问题了! {
"error": {
"errorType": "InvalidGithubToken"
},
"provider": "github"
} |
I also found this problem! {
"error": {
"errorType": "InvalidGithubToken"
},
"provider": "github"
} |
✅ @git268 This issue is closed, If you have any questions, you can comment and reply. |
🎉 This issue has been resolved in version 1.45.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
📦 部署环境
Docker
📌 软件版本
v1.45.0
💻 系统环境
Windows
🌐 浏览器
Edge
🐛 问题描述
左边为Lobechat服务端数据库部署模式而右边为Lobechat客户端数据库模式。对于github中的模型,使用同样的api key,客户端数据库模式可以正常使用。但是,服务端数据库部署模式对github api key检查不通过且无法使用其中的模型,其他服务商模型一切正常。
On the left is the deployment pattern for the Lobechat server-side database, and on the right is the Lobechat client-side database pattern. When using models from GitHub, the client-side database pattern works correctly with the same API key. However, the server-side database deployment pattern fails the GitHub API key check and cannot use models from GitHub, while models from other providers function normally.
📷 复现步骤
使用相同的github api key进行检查,已确认api key准确无误,更换其他github api key仍然无效。
The same GitHub API key was used for verification, and it has been confirmed to be accurate. Replacing it with another GitHub API key still does not work.
🚦 期望结果
希望正常使用github中的模型。
I want to be able to use GitHub models normally.
📝 补充信息
No response
The text was updated successfully, but these errors were encountered: