You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Duplicate files can be created in OCS when you do this:
Create an assistant
On OpenAI, upload a file to the assistant and sync the assistant with OCS
Create a second assistant
Attach the same vector store (using OpenAI's dashboard) to the second assistant and sync this one with OCS
This will create duplicate files in OCS, since we assume that there aren't other assistants using that vector store.
Here's a potential solution. Basically, we let the ToolResource point to the files linked to the other assistant's ToolResource, since the vector stores match. We'll need to redo the implementation of _sync_tool_resource_files_from_openai though, since that will start to delete files if one of the assistants now uses a new vector store. We need to check if the files are being used by another tool resource and only delete them when they are 1. only used by the current tool resource and 2. Not in the new list of file ids that we got from OpenAI.
That said, do we want to continue support for files that was created at OpenAI? I think Brian once mentioned that it's sometimes more convenient to create the assistant at OpenAI and play around with it there before importing it to OCS.
cc @bderenzi@snopoke@stephherbers
The text was updated successfully, but these errors were encountered:
Duplicate files can be created in OCS when you do this:
This will create duplicate files in OCS, since we assume that there aren't other assistants using that vector store.
Here's a potential solution. Basically, we let the
ToolResource
point to the files linked to the other assistant'sToolResource
, since the vector stores match. We'll need to redo the implementation of_sync_tool_resource_files_from_openai
though, since that will start to delete files if one of the assistants now uses a new vector store. We need to check if the files are being used by another tool resource and only delete them when they are 1. only used by the current tool resource and 2. Not in the new list of file ids that we got from OpenAI.That said, do we want to continue support for files that was created at OpenAI? I think Brian once mentioned that it's sometimes more convenient to create the assistant at OpenAI and play around with it there before importing it to OCS.
cc @bderenzi @snopoke @stephherbers
The text was updated successfully, but these errors were encountered: