-
Notifications
You must be signed in to change notification settings - Fork 1
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
Call to createRun() results in error for OpenAI Assistants with "File search" or "Code interpreter" turned on #14
Comments
Hey @jkanalakis. It looks like we missed a few API changes that were added about 2 months ago. Thanks for pointing this out. Please let me know if it works for you now. |
@shipinev Yes, perfect! This works perfectly now with those Assistant settings turned on using the |
Great news! Thanks for checking it out. |
Great, thank you Dmitry. For completeness, will there be a new Git Release to 1.0.2?
Best wishes,
John K.
…________________________________
From: Dmitry Shipinev ***@***.***>
Sent: Thursday, August 1, 2024 2:30 AM
To: exyte/OpenAI ***@***.***>
Cc: John Kanalakis ***@***.***>; Mention ***@***.***>
Subject: Re: [exyte/OpenAI] Call to createRun() results in error for OpenAI Assistants with "File search" or "Code interpreter" turned on (Issue #14)
Closed #14<#14> as completed.
—
Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHXKFPG5ESRCSX5D7BVHALZPH52VAVCNFSM6AAAAABLZU2PBWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTG4ZDEOJXGYZDONQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hello John. Version 1.0.2 is available via SPM (https://github.com/exyte/OpenAI/releases/tag/1.0.2). The CocoaPods update should be available by Monday. |
I really like this library, but I'm having some difficulty with the sample. I only enter my OpenAI Key and the AssistantID and ran the sample project. The OpenAPI Library does not work with some OpenAI Assistant settings as shown below.
When I enable "File search" or "Code interpreter" the API request fails with the client.createRun() call and the following error message appears in the app log. When these options are both turned off, then everything works as expected.
decodingFailed(underlyingError: Swift.DecodingError.dataCorrupted(Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "tools", intValue: nil), _JSONKey(stringValue: "Index 1", intValue: 1), CodingKeys(stringValue: "type", intValue: nil)], debugDescription: "Cannot initialize ToolType from invalid String value file_search", underlyingError: nil)))
Based on this console output. It looks like there's a decoding failure due to an invalid string value "file_search" in the ToolType enum. So I think the ToolType enum also needs to include a case for "file_search".
The text was updated successfully, but these errors were encountered: