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
I called my local Chroma's HTTP API directly to create a collection. However, I accidentally included tenant and database params (since I was also doing some work with Chroma cloud): POST http://localhost:8000/api/v1/collections?tenant=my_tenant&database=my_database.
I got back a 500 error: UniqueConstraintError('Collection 1586333d-0f1d-4f3a-85b3-fc5887ac79f7 already exists')
This error is actively wrong and misleading, given that the true error is an incorrect tenant. It is also highly confusing since it still happens even when the collection name is definitely new and unique, and when get_or_create is set to true.
Note that this is not possible through the Chroma Python API since it gives a user-friendly error when attempting to create a Collection with an invalid tenant.
Versions
Chroma 0.5.6, Python 3.11, MacOS
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
What happened?
I called my local Chroma's HTTP API directly to create a collection. However, I accidentally included
tenant
anddatabase
params (since I was also doing some work with Chroma cloud):POST http://localhost:8000/api/v1/collections?tenant=my_tenant&database=my_database
.I got back a 500 error:
UniqueConstraintError('Collection 1586333d-0f1d-4f3a-85b3-fc5887ac79f7 already exists')
This error is actively wrong and misleading, given that the true error is an incorrect
tenant
. It is also highly confusing since it still happens even when the collection name is definitely new and unique, and when get_or_create is set to true.Note that this is not possible through the Chroma Python API since it gives a user-friendly error when attempting to create a
Collection
with an invalid tenant.Versions
Chroma 0.5.6, Python 3.11, MacOS
Relevant log output
No response
The text was updated successfully, but these errors were encountered: