-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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: FLUSHDB and QWATCH #616
Comments
Hi @apoorvyadav1111 can i work on this one. |
Hi @TheRanomial , I have been working on this and will be raising a PR soon. |
JyotinderSingh
added a commit
that referenced
this issue
Sep 23, 2024
shardul08
pushed a commit
to shardul08/dice
that referenced
this issue
Sep 23, 2024
Co-authored-by: ayadav16 <ayadav7@binghamton.edu> Co-authored-by: Jyotinder Singh <jyotindrsingh@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi everyone,
One observation while working on DBSIZE command is when FLUSHDB is executed before QWATCH, the server does not respond further. I will be adding detailed CLI steps soon to reproduce this issue.
Edit: Replication Steps:
SETUP:
in terminal 2:
subscribe 'SELECT $key, $value WHERE $key like "match:10?:*" ORDER BY $value desc LIMIT 3'
GET Updates:
in terminal 1:
Simultaneously, terminal 2 should update with following result:
Try setting new values in terminal 2 if you would like and terminal 1 will update with new values.
BUG
Run the following command in terminal 1
Now trying setting new values in terminal 2, but this time around terminal 2 will not receive any new update
Please assign this issue to me.
cc: @JyotinderSingh
Thanks
The text was updated successfully, but these errors were encountered: