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(squashing): Reset base command id #2209

Merged
merged 1 commit into from
Nov 26, 2023

Conversation

dranikpg
Copy link
Contributor

@dranikpg dranikpg commented Nov 23, 2023

The multi command squasher takes it's base command id (EXEC or EVAL or EVALSHA) from the context. Then the context is modified to run different commands on it. Whenever collection is interrupted inside pipeline squashing due to a nested multi-transaction, we don't reset the base command when we continue using the context.

@romange
Copy link
Collaborator

romange commented Nov 23, 2023

@dranikpg can you explain the bug?

Signed-off-by: Vladislav Oleshko <vlad@dragonflydb.io>
@dranikpg
Copy link
Contributor Author

Fixed. It has the same stacktrace and cause as #2194, but I don't think it's really it. Simply because it's caused only by a specific command sequence

@romange romange merged commit d6044ed into dragonflydb:main Nov 26, 2023
7 checks passed
@dranikpg dranikpg deleted the fix-squashing-2 branch December 2, 2023 16:45
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.

None yet

3 participants