-
-
Notifications
You must be signed in to change notification settings - Fork 17k
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
[BUG] Error after upgrading to Flowise v2.0.5 with Milvus failing #3046
Comments
I'm having the same problem. Curious if this also affects other people who use Milvus and Flowise 2.x.x? |
I got the same issue with flowise 2.0.7. Here is the debug info from console. ''' Error: Error searching data: {"status":{"extra_info":{},"error_code":"UnexpectedError","reason":"fail to search on QueryNode 2: worker(2) query failed: [json.exception.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid literal; last read: [o","code":65535,"retriable":false,"detail":"failed to search: failed to search/query delegator 2 for channel by-dev-rootcoord-dml_5_452377787821047827v0: fail to search on QueryNode 2: worker(2) query failed: [json.exception.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid literal; last read: [o"},"results":[]} |
+1
It looks like the
|
Flowise 2.1.1 crashes completely for me, when trying to upsert a vector store:
|
Same here is there any workaround ? |
I have submitted a PR that fix the symptoms maybe not the cause of the problem but it works #3336 |
For me this(#3623) change solved the issue |
Description
I recently upgraded Flowise to version 2.0.5. After the upgrade, Milvus started to fail using the same credentials that worked in the previous Flowise version 1.8.4. I am now getting the following error message:
Sample flow that I am testing:
The text was updated successfully, but these errors were encountered: