-
Notifications
You must be signed in to change notification settings - Fork 202
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
feat: support error context in stream/error operations #1149
feat: support error context in stream/error operations #1149
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't had time to look at this super thoroughly yet, but looking good so far. See comments inline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but let's hold off merging this until we have some end-to-end test coverage in (your or my branch of) Wasmtime, e.g. tests that exercise closing with an error and verifying the reader receives it. We should test both the "local" case (i.e. when the same component instance has both ends of the stream/future) and the "remote" case (where the reader and writer ends are owned by different component instances).
Signed-off-by: Victor Adossi <[email protected]>
5a0ac8c
to
7ac0f08
Compare
Signed-off-by: Victor Adossi <[email protected]>
Just a note: there are now working tests that use the functionality in here: |
…nce#1149) * feat: support error context in stream/error operations Signed-off-by: Victor Adossi <[email protected]> * fix: ensure late drop Signed-off-by: Victor Adossi <[email protected]> --------- Signed-off-by: Victor Adossi <[email protected]> Signed-off-by: Joel Dice <[email protected]>
No description provided.