-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
ZHIPUAI_DEFAULT_LIMITS wrong #2323
Comments
🤖 Hey there, @orangeclk! 🤖 I'm Dosu, your friendly neighborhood bot, here to assist you with bugs, answer your queries, and guide you on your way to becoming a contributor. While we wait for a human maintainer to join us, I'm here to help you out. I'll dive into your issue and get back to you with a full answer shortly. Stay tuned! 🚀 |
I learned from the sales staff of Zhipu that the API provided by Zhipu can only support 5 concurrency, and the concurrency setting for the Zhipu API in our code is 50, which resulted in an error in the process. |
🤖 Thank you for bringing this to our attention. It seems like the issue you're experiencing is due to the concurrency setting for the Zhipu API in the dify codebase being set to 50, while the Zhipu API can only support 5 concurrent requests. Unfortunately, I don't have the exact location of the Zhipu API concurrency setting in the dify codebase. However, based on the information you provided, it seems like this setting is causing the issue you're experiencing. As a workaround, you could try reducing the concurrency setting for the Zhipu API in the dify codebase to 5. This should prevent the Zhipu API from being overwhelmed with too many concurrent requests, which seems to be causing the issue you're experiencing. If you're not sure how to change this setting, you could search for it in the If you're still having trouble finding this setting or if changing it doesn't resolve the issue, please provide more information about the issue and I'll do my best to help you resolve it. For example, it would be helpful to know the exact error message you're seeing, as well as any relevant logs or stack traces. I hope this helps! If you have any other questions or need further clarification, please don't hesitate to ask. SourcesThis response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
Self Checks
Dify version
0.5.2
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
When using the Zhipu API to create a knowledge base, it will not be completed for relatively large files.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered: