Issues-translate-bot
commented
1 month ago Bot detected the issue body's language is not English, translate it automatically.
Title: [Bug] After setting the HIDE_USER_API_KEY variable, the Gemini security level option in the settings is not available.
📦 Deployment method
Official installation package, Vercel, Zeabur, Sealos, Netlify, Docker, Other
📌 Software version
v2.14.0
💻 System environment
Other Linux
📌 System version
Debian 12, Kernel 6.1.0-22
🌐 Browser
Firefox
📌 Browser version
115.0esr
🐛 Problem description
As the title states, it is a flaw. After setting that users are not allowed to customize the API, the security level of Gemini cannot be set. Personally, I think there is no connection between security level and custom API.
Variable: HIDE_USER_API_KEY
📷 Steps to reproduce
Just set HIDE_USER_API_KEY to 1
🚦 Expected results
Just put the Gemini security level setting outside the "custom api"
📝 Supplementary information
No remarks, thank you guys
📦 部署方式
Vercel, Zeabur, Sealos, Netlify, Docker
📌 软件版本
v2.14.0
💻 系统环境
Other Linux
📌 系统版本
Debian 12, Kernel 6.1.0-22
🌐 浏览器
Firefox
📌 浏览器版本
115.0 esr
🐛 问题描述
如题，是一个缺陷。当设置了用户不允许自定义api之后，Gemini的安全等级也不能设置了。个人认为安全等级与自定义api没有联系。
变量：
HIDE_USER_API_KEY📷 复现步骤
只需要设置
HIDE_USER_API_KEY为1即可🚦 期望结果
将Gemini安全等级的设置放到“自定义api”之外就行了
📝 补充信息
没有备注，谢谢大佬（们）