Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chroma integration won't work after latest udpate #1136

Open
farzbood opened this issue Oct 15, 2024 · 2 comments
Open

Chroma integration won't work after latest udpate #1136

farzbood opened this issue Oct 15, 2024 · 2 comments
Labels

Comments

@farzbood
Copy link

Describe the bug
The code example from the repo was working before the latest updates for the haystack-ai and chroma-haystack with both models (in-memory and persistent), but it just exit code execution at indexing.run line with no output and/or error code! (log points show that in screenshots below)

Terminal Output: (No Output/Error Code)
image

Debug Console: (Execution never reach the next log point)
image

To Reproduce
Just run the example code in the repo.

Describe your environment (please complete the following information):

  • OS: [Windows10 x86_64]
  • Haystack version: haystack-ai (2.6.1)
  • Integration version: chroma-haystack (0.22.1)
  • chromadb (0.5.13)
@anakin87
Copy link
Member

I cannot reproduce the error.

I tried the following on Ubuntu with Python 3.8 and Python 3.10.

  • Create a new virtual environment
  • pip install chroma-haystack
  • copy the directory example from this repository
  • cd example
  • python example.py

I get the expected result:

{'file_path': '.../example/data/usr_51.txt'} 1.4255602359771729
{'file_path': '.../example/data/usr_41.txt'} 1.4427379369735718
{'file_path': '.../example/data/usr_29.txt'} 1.474898099899292

In our CI, we test the document store on Linux, Windows and MacOS.

Feel free to add more details if the error persists.

@farzbood
Copy link
Author

Hi,
Sorry for late feedback, I've created a clean .env and install chroma-haystack but still got the same results.
So, tracing the code and turns out that the hnswlib in chroma crash the execution, opened an issue there and waiting for the response. will let you know about the results as soon as they respond.
PEACE V

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants