ClientMessageQueueInterceptor continues with subscription processing. #1685
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
|
@dotnet-policy-service agree company="Natural Power Consultants Ltd." |
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.
@chkr1011 Here is a draft PR for the issue I found earlier with the ClientMessageQueueInterceptor with a unit test added to capture the use case of 3 subscribed Clients and a coarse filter in the handler to exclude one of them from receiving messages.
Unit tests I've ran locally... all pass when ran individually be few not so happy when running all together; consistently Disconnect_Clean and Disconnect_Clean_With_Custom_Reason irrespective of target framework, but when ran on their own will pass.