Closed lkiii closed 1 month ago
I am planning to prepare a small example with docker-compose to reproduce this. Will update once ready
After changing the chroma:latest image to chroma:0.5.5 in my docke compose the problem solved~
After changing the chroma:latest image to chroma:0.5.5 in my docke compose the problem solved~
@yenlianglai Please share more details on what you actually changed and what fixed it. Not everyone is basing their container on the chroma:latest
image.
Hi @andreped ,
I had a python program running in docker container with chromadb==0.5.5
, and I have a chromadb instance running in another docker container originally using the latest
tag, the setup running smoothly until weeks ago and raised the TypeError: Collection.__init__() got an unexpected keyword argument 'log_position'
after I rebuild the chromadb instance.
After I change the tag from latest
to 0.5.5
, it runs smoothly again.
@yenlianglai Thanks for the update
Describe the bug Using a stand alone instance of ChromaDB fails. To Reproduce My initiation is:
This fails with
TypeError: Collection.__init__() got an unexpected keyword argument 'log_position'
Expected behavior Vanna not crashing
Error logs/Screenshots
TypeError: Collection.__init__() got an unexpected keyword argument 'log_position'
Desktop (please complete the following information where):
FROM python:3.10-slim
3.10
vanna==0.7.3
Additional context https://github.com/vanna-ai/vanna/issues/249#issuecomment-2395167736
I was debugging all the flow and
log_position
is being returned from the ChromaDB API callExample of the payload: