[wasm] browser http response stream could be seekable - #54749
Merged
pavelsavara merged 3 commits intoJun 30, 2021
Conversation
|
Tagging subscribers to this area: @dotnet/ncl |
- test WebAssemblyEnableStreamingResponse
pavelsavara
force-pushed
the
wasm_BrowserHttpContent_seekable2
branch
from
June 28, 2021 09:36
07103f7 to
443428b
Compare
pavelsavara
marked this pull request as ready for review
June 28, 2021 11:35
Member
Author
|
The failing test is unrelated. |
lewing
reviewed
Jun 28, 2021
marek-safar
approved these changes
Jun 29, 2021
lewing
approved these changes
Jun 29, 2021
ghost
locked as resolved and limited conversation to collaborators
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
As discussed here, the unit test is too restrictive.
Fixes #54159