-
-
Notifications
You must be signed in to change notification settings - Fork 8.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] v1.1.11 Azure Error #3037
Comments
👀 @htdohk Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
Same here (Linux deployment in GCP though), do you have a working version before that @htdohk ? Edit: lobehub/lobe-chat:v1.1.10 seems to not have this issue |
1.1.10 works fine~ |
这个报错信息的endpoint为啥没被变成星号? |
Why is the endpoint of this error message not turned into an asterisk? |
same here, have to rollback to v1.1.10, |
v1.1.12 fixed the Azure Plugin response issue but kept Azure response issue T_T |
@htdohk 我本地测试是正常的,怎么复现? |
@htdohk My local test is normal, how can I reproduce it? |
其实不用任何特殊复现步骤,相同的Vercel环境配置,v1.1.10是好的,11和刚刚的12都是如上的报错。清空网站数据、输入一句“你好”就直接报错了。需要我如何提供更多信息可以再告知我~ |
In fact, there is no need for any special reproduction steps. The same Vercel environment configuration, v1.1.10 is fine, and 11 and 12 just now are reporting the same error. If you need me to provide more information, please let me know~ |
v1.1.12 版本也有这个问题 |
v1.1.12 version also has this problem |
+1 |
+1 |
@arvinxx v1.1.11、12、13问题依旧。无需复现路径,就是任何发送都是回复这个报错。烦请优先解决不然完全无法使用了。 |
@arvinxx The problem remains with v1.1.11, 12, and 13. There is no need to reproduce the path, just any sending will reply to this error. Please resolve it first, otherwise it will be completely unusable. |
After testing it, in Vercel and Docker, server requests will go wrong. |
搜了下 userAgentData 在代码里并不存在,感觉像是依赖问题 |
After searching, userAgentData does not exist in the code. It feels like a dependency issue. |
|
At https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/core/core-rest-pipeline/src/util/userAgentPlatform-browser.mts#L66-L69 I think we should call the node runtime, rather than the browser runtime. |
@BrandonStudio 感觉应该锁一下 |
@BrandonStudio I feel like we should lock the |
@arvinxx Lock is just a workaround, I do think we should switch backend environment to Node. https://github.com/Azure/azure-sdk-for-js/pull/30194/files#r1657657267 |
@BrandonStudio 服务端 runtime 是 edge runtime ,这个能确保发出来的请求是贴近客户这一侧的,以及 stream 时长不超时。切到 node runtime 可以也可以,但是就是默认有 10s 时长限制。 我感觉这个根本上还是这个依赖的问题,应该推 azure 修才是。 |
@BrandonStudio The server-side runtime is edge runtime, which ensures that the request sent is close to the client side and the stream duration does not time out. You can switch to node runtime, but there is a 10s time limit by default. I feel that this is basically a dependency problem, and it should be repaired by Azure. |
OK, waiting for their reply. |
fix in #3066 |
✅ @htdohk This issue is closed, If you have any questions, you can comment and reply. |
…fined localNavigator (#30194) `localNavigator` may be `undefined` at L69. ### Packages impacted by this PR core-rest-pipeline ### Issues associated with this PR lobehub/lobe-chat#3037 ### Describe the problem that is addressed by this PR `localNavigator` may be undefined at L69 on some platform, for example, Edge Runtime.
📦 部署环境
Vercel
📌 软件版本
v1.1.11
💻 系统环境
macOS
🌐 浏览器
Chrome
🐛 问题描述
这个提交之后,Azure崩了。Vercel回滚到上个部署是OK的。
📷 复现步骤
No response
🚦 期望结果
No response
📝 补充信息
No response
The text was updated successfully, but these errors were encountered: