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

[BUG] Running do.when/do.case at the same time crashes Memgraph #442

Open
matea16 opened this issue Jan 29, 2024 · 4 comments
Open

[BUG] Running do.when/do.case at the same time crashes Memgraph #442

matea16 opened this issue Jan 29, 2024 · 4 comments
Assignees
Labels
bug bug community community Effort - Medium Effort - Medium Frequency - EveryTime Frequency - EveryTime Priority - Now Priority - Now Reach - VeryFew Reach - VeryFew Severity - S2 Severity - S2

Comments

@matea16
Copy link

matea16 commented Jan 29, 2024

Running two queries calling do.when/do.case at the same time from a nodeJS client crashes Memgraph. From Discord:
"If I only run one query nothing crashes but as soon as two or more queries get executed simultaneously I need to stop and restart memgraph. I've tried a few other mage algorithms all of which work and do not crash memgraph. Only do.when and do.case exhibit this behaviour."

To replicate, use the following query:

CALL do.when(true, "return true as a","",{})
yield value
return true as a

Source

@matea16 matea16 added Importance - I3 Importance - I3 Severity - S2 Severity - S2 Effort - Unknown Effort - Unknown bug bug community community labels Jan 29, 2024
@imilinovic imilinovic added Effort - Medium Effort - Medium and removed Effort - Unknown Effort - Unknown labels Feb 22, 2024
@hal-eisen-MG hal-eisen-MG added Priority - Next Priority - Next Priority - Now Priority - Now and removed Priority - Next Priority - Next Priority - Now Priority - Now labels Feb 22, 2024
@katarinasupe katarinasupe added Frequency - EveryTime Frequency - EveryTime Reach - VeryFew Reach - VeryFew and removed Importance - I3 Importance - I3 labels Feb 27, 2024
@gitbuda gitbuda removed their assignment Feb 28, 2024
@andrejtonev andrejtonev self-assigned this Feb 29, 2024
@andrejtonev
Copy link

Will be fixed with @Josipmrden 's PR.

@hal-eisen-MG hal-eisen-MG added Priority - Now Priority - Now and removed Priority - Next Priority - Next labels Apr 7, 2024
@Josipmrden
Copy link
Collaborator

Should be resolved but we didn't test this behaviour.

@katarinasupe
Copy link
Contributor

@matea16 can you try it out?

@matea16
Copy link
Author

matea16 commented Apr 12, 2024

It seems to be working, I wasn't able to crash it. I'll ask user to test it out further and check if it works as expected now

@hal-eisen-MG hal-eisen-MG added Priority - Next Priority - Next and removed Priority - Now Priority - Now labels Apr 28, 2024
@hal-eisen-MG hal-eisen-MG added Priority - Now Priority - Now and removed Priority - Next Priority - Next labels May 12, 2024
@hal-eisen-MG hal-eisen-MG added Priority - Next Priority - Next and removed Priority - Now Priority - Now labels Jun 16, 2024
@hal-eisen-MG hal-eisen-MG added Priority - Now Priority - Now and removed Priority - Next Priority - Next labels Oct 20, 2024
@gitbuda gitbuda added Priority - Next Priority - Next and removed Priority - Now Priority - Now labels Oct 27, 2024
@gitbuda gitbuda added Priority - Now Priority - Now and removed Priority - Next Priority - Next labels Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bug community community Effort - Medium Effort - Medium Frequency - EveryTime Frequency - EveryTime Priority - Now Priority - Now Reach - VeryFew Reach - VeryFew Severity - S2 Severity - S2
Projects
Development

No branches or pull requests

7 participants