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

Self-connecting relation could cause crash or unexpected exception #751

Open
Aurora-yzj opened this issue Jul 22, 2024 · 0 comments
Open

Comments

@Aurora-yzj
Copy link

Hi! I have discovered that a node with a self-connecting relation could cause a database crash or raise an unexpected exception Type mismatch: expected Boolean but was String when executing the query. The bug is not relevant to specific API.

The steps to reproduce the bug are as follows.

  1. Start the docker with sudo docker run -p 6379:6379 -p 3000:3000 -it --rm falkordb/falkordb:edge.
  2. Execute the following queries to initialize the basic data. Please note that the relation is from and to the same node.
CREATE (n0 :L28{k161 : -392104257, k162 : -60652336, k158 : false, id : 5, k159 : "dGThjm0QF"});
MATCH (n0 {id : 5}), (n1 {id : 5}) MERGE(n0)-[r :T38{k490 : true, k486 : true, k485 : -1782193271, k487 : true, id : 10, k489 : true}]->(n1);
  1. The following query could cause the database crash, or sometimes unexpected exception Type mismatch: expected Boolean but was String.
MATCH (n0)<-[r0]-(n1), (n2)<-[r1]-(n1), (n0)<-[r2]-(n3) OPTIONAL MATCH (n0)<-[r3]-(n3), (n2)<-[r4]-(n1) WHERE (n1.k159)+'1' CONTAINS '1' AND r3.id <> r4.id AND r4.id <> r3.id AND r3.k485 > r4.k485 AND r4.k485 > r0.k485 return *;

To facilitate root cause analysis, I have compiled a debug version, the attached the log when triggering the crash to the Pastebin (https://pastebin.mozilla.org/BypUBDfp). Hope this could help you. Thanks!

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

No branches or pull requests

1 participant