-
-
Notifications
You must be signed in to change notification settings - Fork 11.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
[Bug] Unsupported 'stream' Parameter Issue with o3-mini Model via GitHub Provider #5644
Comments
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
To resolve the unsupported 'stream' parameter issue with the o3-mini model via the GitHub Provider, ensure that the {
"messages": [
{
"role": "developer",
"content": [...]
}
],
"reasoning_effort": "medium",
"stream": false
} Make sure the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
To resolve the unsupported 'stream' parameter issue with the o3-mini model via the GitHub Provider, ensure that the {
"messages": [
{
"role": "developer",
"content": [...]
}
],
"reasoning_effort": "medium",
"stream": false
} Make sure the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
#5643 相似問題,OpenAI 的推理模型參數的調整,導致後續相關模型都無法順利運作。 |
#5643 Similar issues, the adjustment of the user's reasoning model parameters, resulting in subsequent related models that cannot work smoothly. |
📦 Environment
Docker
📌 Version
v1.49.5
💻 Operating System
macOS
🌐 Browser
Chrome
🐛 Bug Description
The error occurs when attempting to call the o3-mini model via the GitHub Provider, as the 'stream' parameter is set to true, which is unsupported for this model and must be set to false instead.
📷 Recurrence Steps
No response
🚦 Expected Behavior
No response
📝 Additional Information
No response
The text was updated successfully, but these errors were encountered: