This repository was archived by the owner on Sep 8, 2025. It is now read-only.
implement new stream/future trap conditions
#215
Merged
Conversation
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
As of WebAssembly/component-model#524, we now trap if a guest tries to use a stream or future handle (besides dropping it) after it is "done" (see that PR for what "done" means). This required more careful tracking of the state of each end of the stream or future. In the process of debugging this into shape, I added some trace logging and addressed a couple of issues I noticed: - `wasi-http`'s `Response::into_http` wasn't noticing a non-empty buffer at the end of a stream - the `p3_http_middleware` test was not clearing its buffer before each read Signed-off-by: Joel Dice <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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 of WebAssembly/component-model#524, we now trap if a guest tries to use a stream or future handle (besides dropping it) after it is "done" (see that PR for what "done" means). This required more careful tracking of the state of each end of the stream or future.
In the process of debugging this into shape, I added some trace logging and addressed a couple of issues I noticed:
wasi-http'sResponse::into_httpwasn't noticing a non-empty buffer at the end of a streamp3_http_middlewaretest was not clearing its buffer before each read