-
-
Notifications
You must be signed in to change notification settings - Fork 13.4k
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
Issues with Blackbox Provider #2433
Comments
I asked this same question and the answer is here:
I tested this manually with Blackbox in g4f gui, sending messages one at a time and testing the system prompt and found out that Blackbox randomly breaks, ignoring the system prompt and such after responding due to the reasons above. Yup! Nothing that can be done about it sadly... |
Now, it means that it can't be fixed? |
And there is an issue with Copilot Provider. I wrote a long system prompt to Copilot provider and when I ask something to Copilot provider it says: "RuntimeError: Error: {'event': 'error', 'id': '0', 'errorCode': 'text-too-long'}" |
@DeveleplorAbdullahH Hi. Regarding the issue with blackbox. No, g4f can't fix it because the problem is on the provider's side. Technically, you can implement a Json or similar file where you will locally store instructions, dialogue, etc. and let the AI process it before each request, but this will greatly increase the load on the provider. Copilot error says that you have exceeded the context limit on input parameters. Try to reduce them. The size of the limits is set by the providers themselves, as well as the models used. |
There are so many issues with Blackbox provider. It can't read the system prompt and gpt-4o model can not answer. Maybe, there are issues with the servers.
The text was updated successfully, but these errors were encountered: