-
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/7.0] [browser] fix asset counting after download retry #82617
[release/7.0] [browser] fix asset counting after download retry #82617
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThis is simplified version of the https://github.com/dotnet/runtime/pull/81886/files Fixes #82271 Customer ImpactInternally detected problem on CI TestingManual testing RiskTBD
|
✅Manual tests work. |
Approved by Tactics. |
This is simplified version of the https://github.com/dotnet/runtime/pull/81886/files
Fixes #82271
Customer Impact
Internally detected problem on CI.
The issue is caused by counting download retry multiple times.
Only when the retry is caused by download fail during
await response.arrayBuffer()
but after HTTP headers are already fetched.That could be TCP failure and similar issues.
Testing
Added sample code with test for aborted HTTP stream and HTTP code 500 as well.
Manual testing
Risk
The download retry logic is complex.
This code path is relevant for WASM application which don’t use blazor (small audience).