-
Notifications
You must be signed in to change notification settings - Fork 103
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 client invocation bug with multiple endpoints #2154
base: dev
Are you sure you want to change the base?
Conversation
427b44c
to
0f8a61e
Compare
6f3059e
to
9431689
Compare
src/Microsoft.Azure.SignalR.Common/ServiceConnections/MultiEndpointMessageWriter.cs
Show resolved
Hide resolved
src/Microsoft.Azure.SignalR/ClientInvocation/CallerClientResultsManager.cs
Show resolved
Hide resolved
if (serviceMessage is ClientInvocationMessage invocationMessage) | ||
{ | ||
// Accroding to target endpoints in method `WriteMultiEndpointMessageAsync` | ||
_clientInvocationManager.Caller.SetAckNumber(invocationMessage.InvocationId, TargetEndpoints.Length); |
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.
when TargetEndpoints.Length
is 0, the result is OK?
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.
class AckHandler
could handle such condition correctly. Refer to its method SetExpectedCount
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.
075f8ed
to
68b7aa7
Compare
Summary of the changes (Less than 80 chars)