-
Notifications
You must be signed in to change notification settings - Fork 56
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
Feature/rea 1808 use separate channel object #1655
Merged
mschristensen
merged 13 commits into
experimental-v2/channel-and-consumer-group
from
feature/REA-1808-use-separate-channel-object
Mar 1, 2024
Merged
Feature/rea 1808 use separate channel object #1655
mschristensen
merged 13 commits into
experimental-v2/channel-and-consumer-group
from
feature/REA-1808-use-separate-channel-object
Mar 1, 2024
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
Similar to the active channel, we need to avoid conflicts.
We store the current active set of members in the hashring.
Messages can be delivered more than once during a consumer group rescaling event, so deduplicate the results when checking the end condition.
github-actions
bot
temporarily deployed
to
staging/pull/1655/features
February 29, 2024 17:43
Inactive
github-actions
bot
temporarily deployed
to
staging/pull/1655/typedoc
February 29, 2024 17:44
Inactive
github-actions
bot
temporarily deployed
to
staging/pull/1655/bundle-report
February 29, 2024 17:44
Inactive
VeskeR
approved these changes
Mar 1, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, some minor test comments, but they are not blockers really
The Channels object used by the ChannelGroup for internal channel operations no longer shares the same object exposed on the client via the .channels() method. This is to ensure that independent usage of an individual channel that happens to be included in a channel group is not impacted by its usage in the channel group.
Now that we can correctly handle a channel group and channel being used independently from the same client, this tidies up the leave test to remove the additional client previously needed.
mschristensen
force-pushed
the
feature/REA-1808-use-separate-channel-object
branch
from
March 1, 2024 09:52
08259c4
to
2193fa0
Compare
mschristensen
merged commit Mar 1, 2024
2906280
into
experimental-v2/channel-and-consumer-group
4 of 12 checks passed
This was referenced Mar 1, 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.
Depends on #1651