-
Notifications
You must be signed in to change notification settings - Fork 153
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
CreateAssistantToolResources fields must be optional? #251
Comments
vrurg
added a commit
to vrurg/async-openai
that referenced
this issue
Jul 30, 2024
For `CreateAssistantToolFileSearchResources` struct the API expects only one of the two fields to be used. Even an empty array is not accepted if the other field contains a value. Thus making both `vector_store_ids` and `vector_stores` optional is the way to go. Fixes 64bit#251
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was working on code that creates an assistant with attached pre-existing vector store. Unfortunately, it doesn't seem to be possible. Since both fields are currently non-
Option
, the only possible way to create an instance is something like:The point is that one has to specify both
vector_store_ids
andvector_stores
. Unfortunately, the API doesn't accept this kind of request:From the error message I conclude that the right way is to make both fields optional.
Now I wonder how do I attach the vector store to a new assistant...
The text was updated successfully, but these errors were encountered: