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

chore: Use pipeline whenever possible in pytests #4459

Closed
wants to merge 1 commit into from

Conversation

chakaz
Copy link
Collaborator

@chakaz chakaz commented Jan 15, 2025

If we don't use FakeRedis we can always use pipeline / multi-exec. However, we can also use FakeRedis with multi-exec during migrations, because migrations wait for such operations to complete before finalization. We can't use FakeRedis with regular pipelines though because it may cause non deterministic comparisons.

If we don't use FakeRedis we can always use pipeline / multi-exec.
However, we can also use FakeRedis with multi-exec during migrations,
because migrations wait for such operations to complete before
finalization. We can't use FakeRedis with regular pipelines though
because it may cause non deterministic comparisons.
@chakaz
Copy link
Collaborator Author

chakaz commented Jan 15, 2025

@adiholden I think that this PR won't work, because in cases of OOM we reject commands (and break the transaction-ness of MULTI/EXEC)...

@adiholden
Copy link
Collaborator

@adiholden I think that this PR won't work, because in cases of OOM we reject commands (and break the transaction-ness of MULTI/EXEC)...

Ok I understand

@chakaz chakaz closed this Jan 15, 2025
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.

2 participants