-
Notifications
You must be signed in to change notification settings - Fork 990
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
v1.25.0 crashes when running some BullMQ tests #4113
Comments
@manast thanks for notifying us. Can you please remind me how to run the test suite? |
nm, figured this out from your actions:
with local dragonfly: |
Hi there. This same issue broke our production :D Waiting for a fix. Reverting to |
Good idea, I pushed the latest tag to point to v1.24.0 for now. |
The regression was caused by #3947 and it causes crashes in bullmq. It has not been found till now because python client sends commands in uppercase. Fixes #4113 Signed-off-by: Roman Gershman <[email protected]>
The regression was caused by #3947 and it causes crashes in bullmq. It has not been found till now because python client sends commands in uppercase. Fixes #4113 Signed-off-by: Roman Gershman <[email protected]> Co-authored-by: Kostas Kyrimis <[email protected]>
Describe the bug
Since v1.25.0 released today, BullMQ's test suite produces a hard crash in dragonfly's server.
To Reproduce
Steps to reproduce the behavior:
Just run the test suite but one of the tests that reproduces the issue is the first test in test_concurrency.ts: https://github.com/taskforcesh/bullmq/blob/master/tests/test_concurrency.ts#L33
Expected behavior
Should not crash and test should pass
Screenshots
Environment (please complete the following information):
uname -a
Reproducible Code Snippet
Additional context
This is the output of the server when it crashes:
This is the last command sent to Dragonfly and that triggers the crash:
Let me know if you need more info.
The text was updated successfully, but these errors were encountered: