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

fix: allow SELECT in multi/exec if it's a noop #4146

Merged
merged 1 commit into from
Nov 18, 2024
Merged

fix: allow SELECT in multi/exec if it's a noop #4146

merged 1 commit into from
Nov 18, 2024

Conversation

romange
Copy link
Collaborator

@romange romange commented Nov 18, 2024

Fixes #4120

Fixes #4120

Signed-off-by: Roman Gershman <roman@dragonflydb.io>
@romange romange merged commit d467a34 into main Nov 18, 2024
12 checks passed
@romange romange deleted the Pr2 branch November 18, 2024 20:27
romange added a commit that referenced this pull request Nov 19, 2024
Fixes #4150. The failure can be reproduced with high probability on ARM via
`pytest dragonfly/replication_test.py -k test_replication_all[df_factory0-mode0-8-t_replicas3-seeder_config3-2000-False]`

Not sure why this barrier is needed but #4146 removes the barrier
which breaks a gentle balance in the code in unexpected way.

Signed-off-by: Roman Gershman <roman@dragonflydb.io>
romange added a commit that referenced this pull request Nov 20, 2024
Fixes #4150. The failure can be reproduced with high probability on ARM via
`pytest dragonfly/replication_test.py -k test_replication_all[df_factory0-mode0-8-t_replicas3-seeder_config3-2000-False]`

Not sure why this barrier is needed but #4146 removes the barrier
which breaks a gentle balance in the code in unexpected way.

Signed-off-by: Roman Gershman <roman@dragonflydb.io>
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

Successfully merging this pull request may close these issues.

MULTI does not allow SELECT
2 participants