Wasmtime GitHub notifications bot (Aug 25 2026 at 18:06): Wasmtime GitHub notifications bot (Aug 25 2026 at 18:06):rvolosatovs opened PR #14206 from rvolosatovs:stream-future-forward to bytecodealliance:main:
implement
{future,stream}.forwardas defined in https://github.com/WebAssembly/component-model/pull/709I have run the test suite from CM PR against this implementation, but I did not update the submodule, since there are a few test cases in the spec repo
main, which Wasmtime currently fails.
Wasmtime GitHub notifications bot (Aug 25 2026 at 18:08):rvolosatovs updated PR #14206.
Wasmtime GitHub notifications bot (Aug 25 2026 at 18:22):rvolosatovs edited PR #14206:
implement
{future,stream}.forwardas defined in https://github.com/WebAssembly/component-model/pull/709I have run the test suite from CM PR against this implementation, but I did not update the submodule, since there are a few test cases in the spec repo
main, which Wasmtime currently fails.The test cases are entirely LLM-generated, mostly based on the Python host tests in the spec (which are also LLM-generated)
The implementation is LLM-generated, but based on a rough sketch I wrote by hand.
Wasmtime GitHub notifications bot (Aug 25 2026 at 19:51):github-actions[bot] added the label wasmtime:api on PR #14206.
Wasmtime GitHub notifications bot (Aug 27 2026 at 16:43):fitzgen added the label wasm-proposal:component-model-async on PR #14206.
Wasmtime GitHub notifications bot (Oct 05 2026 at 16:23):rvolosatovs updated PR #14206.
Wasmtime GitHub notifications bot (Oct 05 2026 at 16:27):rvolosatovs edited PR #14206:
implement
{future,stream}.forwardas defined in https://github.com/WebAssembly/component-model/pull/717I have run the test suite from CM PR against this implementation, but I did not update the submodule, since there are a few test cases in the spec repo
main, which Wasmtime currently fails.The test cases are entirely LLM-generated, mostly based on the Python host tests in the spec (which are also LLM-generated)
The implementation is LLM-generated, but based on a rough sketch I wrote by hand.
Wasmtime GitHub notifications bot (Oct 05 2026 at 16:28):rvolosatovs edited PR #14206:
implement
{future,stream}.forwardas defined in https://github.com/WebAssembly/component-model/pull/717The test cases are entirely LLM-generated, mostly based on the Python host tests in the spec
The implementation is LLM-generated, but based on a rough sketch I wrote by hand.
Wasmtime GitHub notifications bot (Oct 05 2026 at 17:48):github-actions[bot] added the label fuzzing on PR #14206.
Wasmtime GitHub notifications bot (Oct 05 2026 at 17:48):github-actions[bot] added the label wasmtime:c-api on PR #14206.
Wasmtime GitHub notifications bot (Oct 05 2026 at 17:48):github-actions[bot] added the label wasmtime:config on PR #14206.
Wasmtime GitHub notifications bot (Oct 05 2026 at 18:54):github-actions[bot] commented on PR #14206:
Subscribe to Label Action
cc @fitzgen
<details>
This issue or pull request has been labeled: "fuzzing", "wasm-proposal:component-model-async", "wasmtime:api", "wasmtime:c-api", "wasmtime:config"Thus the following users have been cc'd because of the following labels:
- fitzgen: fuzzing
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
Wasmtime GitHub notifications bot (Oct 05 2026 at 19:54):github-actions[bot] commented on PR #14206:
Label Messager: wasmtime:config
It looks like you are changing Wasmtime's configuration options. Make sure to
complete this check list:
[ ] If you added a new
Configmethod, you wrote extensive documentation for
it.<details>
Our documentation should be of the following form:
```text
Short, simple summary sentence.More details. These details can be multiple paragraphs. There should be
information about not just the method, but its parameters and results as
well.Is this method fallible? If so, when can it return an error?
Can this method panic? If so, when does it panic?
Example
Optional example here.
```</details>
[ ] If you added a new
Configmethod, or modified an existing one, you
ensured that this configuration is exercised by the fuzz targets.<details>
For example, if you expose a new strategy for allocating the next instance
slot inside the pooling allocator, you should ensure that at least one of our
fuzz targets exercises that new strategy.Often, all that is required of you is to ensure that there is a knob for this
configuration option in [wasmtime_fuzzing::Config][fuzzing-config] (or one
of its nestedstructs).Rarely, this may require authoring a new fuzz target to specifically test this
configuration. See [our docs on fuzzing][fuzzing-docs] for more details.</details>
[ ] If you are enabling a configuration option by default, make sure that it
has been fuzzed for at least two weeks before turning it on by default.[fuzzing-config]: https://github.com/bytecodealliance/wasmtime/blob/ca0e8d0a1d8cefc0496dba2f77a670571d8fdcab/crates/fuzzing/src/generators.rs#L182-L194
[fuzzing-docs]: https://docs.wasmtime.dev/contributing-fuzzing.html
<details>
To modify this label's message, edit the <code>.github/label-messager/wasmtime-config.md</code> file.
To add new label messages or remove existing label messages, edit the
<code>.github/label-messager.json</code> configuration file.</details>
Last updated: Oct 11 2026 at 02:20 UTC