Preparation for redis omniqueue usage #1237
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
svix-jplatte
force-pushed
the
jplatte/redis-omniqueue-prep
branch
3 times, most recently
from
cfa089a
to
50eb3f9
Compare
Merged
svix-jplatte
force-pushed
the
jplatte/redis-omniqueue-prep
branch
from
50eb3f9
to
a373bdd
Compare
… to stop relying on receive_all always just return a single item.
svix-james
approved these changes
Feb 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The redis omniqueue PR (#1228) is a bit on the large side
and still has one inexplicably failing test. Pull out one unrelated redis refactoring and the omniqueue upgrade (also for bridge, new in this PR) to land changes incrementally.