-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[release/8.0][browser] BrowserWebSocket.ReceiveAsync after server initiated close #97002
[release/8.0][browser] BrowserWebSocket.ReceiveAsync after server initiated close #97002
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsFixes #96359 DescriptionPending incoming messages are lost after we receive Customer ImpactThis is user reported issue #96359 RegressionProbably introduced in Net7 TestingNew automated unit tests in this PR. Existing automated unit tests. RiskThis is non-trivial change.
|
/azp run runtime-wasm |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Today is Code Complete for the February Release. |
5e9e29f
into
dotnet:release/8.0-staging
Fixes #96359
main PR for Net9 #96618 , this is not 1-to-1 merge.
Description
Pending incoming WebSocket messages are lost after we receive
close
message from the server side.Customer Impact
This is user reported issue #96359
Regression
Probably introduced in Net7
Testing
New automated unit tests in this PR. Existing automated unit tests.
Risk
This is non-trivial change.
The impact is users of .Net on the browser, typically Blazor.