Max Isom

I started implementing the proposed API above, but after playing around with it I think it adds some cognitive overhead for not much benefit (when should I call `batch_upsert()` instead...

Because Chroma doesn't support transactions, automatically batching would raise the same issues I noted here: https://github.com/chroma-core/chroma/issues/2282#issuecomment-2263927583. How do we report a partially succeeded state? It could work if we ignored...

> In the case of a partially failed batch, the simplest thing to do would be assume the user would run the same operation again; in the case of `.add`,...

> The thing we're trying to help / solve for users is that one of the first things they want to do is load a bunch of data into Chroma,...

> How do you mean 'take over the terminal' ? e.x. if you print something else during the operation the output isn't great: https://github.com/user-attachments/assets/38580a69-1725-474e-ac45-b4499ac3f9bb (This is with tqdm, which is...

`rich` handles this better: https://github.com/user-attachments/assets/ff43644b-05ec-4171-b944-89bb6e7b26b0

@HammadB had some similar concerns about printing progress by default and transparently batching since the resulting guarantees may be different. How does this API feel? (This is basically what I...

Just to confirm, you invited Muse to your server with the logged invite URL? I would try kicking Muse and re-inviting, based on the logs it seems like your Muse...

Hmm, are you able to invite Muse to a fresh server just to see if it's an issue with your particular server?

> Should we let a user give us IDs only sometimes, e.g. by allowing None in the ids list? My gut says no, but worth thinking about. I don't think...