[Bug] groq api 代理的bug（版本0.156.2）

[xzy103]

💻 系统环境

Ubuntu

📦 部署环境

Docker

🌐 浏览器

Edge

🐛 问题描述

至0.156.0版本开始，支持设置groq的api代理链接了，但是在我发现如果勾选了使用客户端请求模式后，实际走的还是原来的链接，并没有走代理链接，造成连接失败。

🚦 期望结果

No response

📷 复现步骤

No response

📝 补充信息

No response

[lobehubbot]

👀 @xzy103

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

💻 System environment

Ubuntu

📦 Deployment environment

Docker

🌐 Browser

Edge

🐛 Problem description

Starting from the 0.156.0 version, setting up groq's api proxy link is supported. However, I found that if Use client request mode is checked, the original link is actually used and no proxy link is used. , causing the connection to fail.

🚦 Expected results

No response

📷 Steps to reproduce

No response

📝 Supplementary information

No response

[AppleRiven]

这里确实有bug，感觉需要调整一下逻辑，填写了API代理地址之后，下面的开关就无效了。删除代理地址，开关隐藏，但不会自动关闭。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

There is indeed a bug here, and I feel that the logic needs to be adjusted. After filling in the API proxy address, the following switches are invalid. Remove the proxy address and the switch is hidden but will not be turned off automatically.

[lobehubbot]

✅ @xzy103

This issue is closed, If you have any questions, you can comment and reply.
此问题已经关闭。如果您有任何问题，可以留言并回复。

[lobehubbot]

🎉 This issue has been resolved in version 1.1.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀