-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
#930 The WebSocket is in an invalid state ('Aborted') for this operation #1030 #1576
Conversation
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.
I do NOT see any fixes!
I see extra code only with extra post-action.
Could you add a couple of unit tests please?
Also, could you write at least one acceptance test please?
await destination.CloseOutputAsync(WebSocketCloseStatus.EndpointUnavailable, null, cancellationToken); | ||
if (destination.State == WebSocketState.Open || destination.State == WebSocketState.CloseReceived) | ||
{ | ||
await destination.CloseOutputAsync(WebSocketCloseStatus.EndpointUnavailable, null, cancellationToken); | ||
} |
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.
Simple logical challenge:
How many times will the action be applied here?
Once or twice?
The action is CloseOutputAsync
.
await destination.CloseOutputAsync(WebSocketCloseStatus.EndpointUnavailable, null, cancellationToken); | ||
if (destination.State == WebSocketState.Open || destination.State == WebSocketState.CloseReceived) | ||
{ | ||
await destination.CloseOutputAsync(WebSocketCloseStatus.EndpointUnavailable, null, cancellationToken); | ||
} |
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.
Why do you apply the same action twice?
The action is CloseOutputAsync
.
I'm closing this PR as I can't remember what it was actually about and the original author is actively communicating on #1030 |
Reopened PR: #1030
tdejong-tools4ever commented on Sep 30, 2019