-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Unknown parameter for CreateThreadAndRun method #773
Comments
I think this PR is aiming to fix this issue. @rasmusviben i'm seeing issues where the run states are never making it out of queued. Wondering if you'd seen this (maybe prior to v1.26.0) |
Alright - do you know the ETA for getting that PR into a new release? :) I tried downgrading to 1.24 and 1.25, but then new exception is thrown:
|
Having the same issue. Downgrading to 1.24 worked for me though. |
I assume that a problem here is outdated |
Need help getting a PR across the line? I'm seeing this error as well. |
FileIDs on ThreadMessage isn't supported anymore, but Content can be an array. Fixes: sashabaranov#773
FileIDs on ThreadMessage isn't supported anymore, but Content can be an array. Fixes: sashabaranov#773
#764 doesn't seem to fix the OP's issue (or mine) so I opened a PR which works, but has a breaking change. Do we have a policy for handling breaking changes better? |
FileIDs on ThreadMessage isn't supported anymore, but Content can be an array. Fixes: sashabaranov#773
Any updates on this? |
Describe the bug
When calling the CreateThreadAndRun method, the response is 400 due to unknown parameter in the ThreadRequest: thread.messages[0].file_ids
To Reproduce
Run follow code given assistant is created:
Expected behavior
Expected that the request was succesfull and not throwing 400 bad request for that parameter.
Screenshots/Logs
2024/06/19 20:19:55 CreateThreadAndRun error: error, status code: 400, message: Unknown parameter: 'thread.messages[0].file_ids'.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: