[NativeAOT-LLVM] disable SocketsHttpHandler support for WASI #2667
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
Disabling this until System.Net.Sockets support comes to WASI. Signed-off-by: Matthew Fisher <[email protected]>
|
related to #2614. |
jkotas
added
the
area-NativeAOT-LLVM
jkotas
approved these changes
Aug 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Disabling this until
System.Net.Socketssupport comes to WASI via wasi-sockets. Many libraries (such as grpc-dotnet) check the value ofSocketsHttpHandler.IsSupportedto see if it needs to fall back from a sockets-based handler to a basic HTTP handler.If this is not the correct location to update, let me know and I'd be happy to amend the PR.