-
Notifications
You must be signed in to change notification settings - Fork 13
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
RecursionError when using qdrant-haystack 7.0.0 with Hayhooks #43
Comments
Thanks for the fix @mpangrazzi! I think that resolved the recursion error. However, I've only had partial success while trying to deploy a pipeline (with and without Qdrant components) so i didn't get to fully testing it. I can't seem to get any pipeline deployed since I am now encountering errors in the hayhooks server as well as in the client. The errors are described in #47. |
@mpangrazzi I've tested a few different deployments and they work smoothly now. Thank you for your time! The client still throws a |
@mpangrazzi of course, excuse the oversight. What I'm referring to is that if the Hayhooks server encounters an unhandled exception during deployment ( To provoke an error during deployment you can use this file from #44 and make sure to not set the |
Problem Description
Our pipeline definition (see below) runs into a
RecursionError: maximum recursion depth exceeded
exception. We're usingQdrantDocumentStore
andQdrantEmbeddingRetriever
fromqdrant-haystack
which seems to be causing the error since running the pipeline with its in-memory counterparts instead is successful.Expected Behaviour
The pipeline should run without throwing an exception, correctly handling the Qdrant integration types.
Observed Behavior
Stacktrace
pipeline.yml
Hypothesis
The recursion happens when
handle_unsupported_types
processes nested or generic types likeqdrant_client.http.models.models.Filter
.I've monkey-patched a print statement in
handle_unsupported_types
to have a look at its parameters causing the recursion:which repeatedly prints the following before also throwing the exception:
Console Prints
It seems like
handle_unsupported_types
doesn't terminate for certain nested generic types. Manually increasing recursion depth might solve this.requirements.txt
The text was updated successfully, but these errors were encountered: