William Black

Test workflows are passing now that we xfail and skip classes with failing tests

> @embr So I just ran `pytest --runxfail` now in a fresh virtual environment but was unable to run anything - I got a bunch of errors collecting tests. Every...

@embr There are many many errors, so for space, I am including just the first two. The vast majority of them are `TypeError: can't (safely) pickle generator objects` that you...

> 3.10.12 Interesting. I was able to run the tests using a fresh 3.10.12 virtual environment and get basically the same pickle errors on my machine. I get the following...

It seems that there is some issue with pickling and using `pytest`. The pickling errors do not show up outside of `pytest`. I'm not sure what it is, and searching...

> For example, I looked into the `pytest` issue you shared ([pytest-dev/pytest#12448](https://github.com/pytest-dev/pytest/issues/12448)), and wondered whether adding `--assert=plain` might fix the issue. Have you tried this? [This comment](https://github.com/pytest-dev/pytest/issues/12448#issuecomment-2162075684) seems to indicate...

> Absolutely understandable. @smokestacklightnin Let's swap back to running `unittest` for now. Once a workflow is up and running on every PR, let's revisit this later on. At the same...

Closing this PR as superseded by #189 CC: @peytondmurray

Currently, the only option to create an async client for ChromaDB is to use [`AsyncHttpClient`](https://docs.trychroma.com/reference/python/client#asynchttpclient). This _cannot_ be used in a Python class initializer because Python class initializers must necessarily...

@pmeier do you have any input?