fix(exec): sync TLS listener and stream applications with upstream #2240
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
- Add missing method implementations from upstream - Remove implementations, that are not present upstream - Add TODOs and file issues for missing implementations Signed-off-by: Roman Volosatovs <roman@profian.com>
rvolosatovs
force-pushed
the
fix/tls-upstream
branch
from
961c9ef
to
97dacb1
Compare
rvolosatovs
requested review from
npmccallum,
haraldh and
bstrie
as code owners
haraldh
approved these changes
Sep 27, 2022
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.
Sync with https://github.com/bytecodealliance/wasmtime/blob/ee2ef5bdd02ac75eff284e84dc9a8dcdf3d6e2c6/crates/wasi-common/cap-std-sync/src/net.rs
Refs #2241 #2242 #2243