-
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
[browser][MT] Use auto thread dispatch in HTTP #95370
Merged
pavelsavara
merged 25 commits into
dotnet:main
from
pavelsavara:browser_jsimport_sc_dispatch
Jan 21, 2024
Merged
[browser][MT] Use auto thread dispatch in HTTP #95370
pavelsavara
merged 25 commits into
dotnet:main
from
pavelsavara:browser_jsimport_sc_dispatch
Jan 21, 2024
Conversation
This file contains 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
pavelsavara
added
arch-wasm
WebAssembly architecture
area-System.Runtime.InteropServices.JavaScript
os-browser
Browser variant of arch-wasm
labels
Nov 28, 2023
Tagging subscribers to 'arch-wasm': @lewing Issue Detailsnull
|
This was referenced Nov 30, 2023
pavelsavara
force-pushed
the
browser_jsimport_sc_dispatch
branch
2 times, most recently
from
December 4, 2023 20:56
3cf1400
to
6c3bf7f
Compare
This comment was marked as outdated.
This comment was marked as outdated.
pavelsavara
force-pushed
the
browser_jsimport_sc_dispatch
branch
2 times, most recently
from
December 12, 2023 13:32
ec2fc61
to
730b5ec
Compare
pavelsavara
force-pushed
the
browser_jsimport_sc_dispatch
branch
2 times, most recently
from
December 16, 2023 21:17
8b6ae1e
to
b22f15c
Compare
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
This comment was marked as outdated.
This comment was marked as outdated.
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
# Conflicts: # src/libraries/System.Runtime.InteropServices.JavaScript/src/CompatibilitySuppressions.xml
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
maraf
approved these changes
Jan 19, 2024
This was referenced Jan 19, 2024
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
tmds
pushed a commit
to tmds/runtime
that referenced
this pull request
Jan 23, 2024
Co-authored-by: campersau <buchholz.bastian@googlemail.com> Co-authored-by: Marek Fišera <mara@neptuo.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
arch-wasm
WebAssembly architecture
area-System.Runtime.InteropServices.JavaScript
os-browser
Browser variant of arch-wasm
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.
HTTP
HttpController
helper object on the JavaScript sidehttp_wasm_transform_stream_abort
into regular abort. Abort request will also abort response if any.WasmFetchResponse
toBrowserHttpController
CallFetch
and header construction logic to it.closePromise
andfetchPromise
and observing the errorsWasmHttpWriteStream
toBrowserHttpWriteStream
WebWorkerTest
which test client usage across thread boundaries.System.Net.Http.Functional.Tests
, now also run xunit on thread pool in MTOther
JSWebWorker
setup_proxy_console
for early disconnectSynchronizationContextExtension
JSHost.CurrentOrMainJSSynchronizationContext
Fixes #96173
Fixes #75123