Wasmtime GitHub notifications bot (Apr 27 2026 at 22:08): Wasmtime GitHub notifications bot (Apr 27 2026 at 22:08):alexcrichton opened PR #13217 from alexcrichton:gate-sync to bytecodealliance:main:
This commit renames the previous
wasm_component_model_async_builtinsfeature towasm_component_model_more_async_builtinsand then moves synchronous future/stream reads/writes behind this feature. This is inspired by bytecodealliance/wasmtime#13212 and corresponds to WebAssembly/component-model#641 plus bytecodealliance/wasm-tools#2507.<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Apr 27 2026 at 22:08):alexcrichton requested dicej for a review on PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 01:16):github-actions[bot] added the label wasmtime:config on PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 01:16):github-actions[bot] added the label wasmtime:api on PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 02:35):github-actions[bot] commented on PR #13217:
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>
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:47):alexcrichton updated PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:47):alexcrichton has marked PR #13217 as ready for review.
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:47):alexcrichton requested fitzgen for a review on PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:47):alexcrichton requested wasmtime-core-reviewers for a review on PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:47):alexcrichton requested wasmtime-fuzz-reviewers for a review on PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:47):alexcrichton requested wasmtime-default-reviewers for a review on PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:48):alexcrichton updated PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:49):alexcrichton commented on PR #13217:
This now pulls in an update-to wasm-tools and shoudl be good to go modulo CI
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:49):alexcrichton edited a comment on PR #13217:
This now pulls in an update-to wasm-tools and shoudl be good to go modulo CI/review
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:52):alexcrichton edited a comment on PR #13217:
This now pulls in an update-to wasm-tools and should be good to go modulo CI/review
Wasmtime GitHub notifications bot (Apr 28 2026 at 16:54):alexcrichton updated PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 17:08)::thumbs_up: fitzgen submitted PR review.
Wasmtime GitHub notifications bot (Apr 28 2026 at 18:31):alexcrichton updated PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 18:31):alexcrichton has enabled auto merge for PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 18:47):alexcrichton added PR #13217 Gate synchronous future/stream read/write separately to the merge queue.
Wasmtime GitHub notifications bot (Apr 28 2026 at 19:11):github-merge-queue[bot] removed PR #13217 Gate synchronous future/stream read/write separately from the merge queue.
Wasmtime GitHub notifications bot (Apr 28 2026 at 19:35)::thumbs_up: dicej submitted PR review.
Wasmtime GitHub notifications bot (Apr 28 2026 at 20:05):alexcrichton updated PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 20:05):alexcrichton has enabled auto merge for PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 23:01):github-actions[bot] added the label fuzzing on PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 23:01):github-actions[bot] added the label wasmtime:c-api on PR #13217.
Wasmtime GitHub notifications bot (Apr 28 2026 at 23:02):github-actions[bot] commented on PR #13217:
Subscribe to Label Action
cc @fitzgen
<details>
This issue or pull request has been labeled: "fuzzing", "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 (Apr 29 2026 at 00:55):alexcrichton updated PR #13217.
Wasmtime GitHub notifications bot (Apr 29 2026 at 01:11):alexcrichton added PR #13217 Gate synchronous future/stream read/write separately to the merge queue.
Wasmtime GitHub notifications bot (Apr 29 2026 at 01:34):github-merge-queue[bot] removed PR #13217 Gate synchronous future/stream read/write separately from the merge queue.
Wasmtime GitHub notifications bot (Apr 29 2026 at 13:02):alexcrichton added PR #13217 Gate synchronous future/stream read/write separately to the merge queue.
Wasmtime GitHub notifications bot (Apr 29 2026 at 13:28)::check: alexcrichton merged PR #13217.
Wasmtime GitHub notifications bot (Apr 29 2026 at 13:28):alexcrichton removed PR #13217 Gate synchronous future/stream read/write separately from the merge queue.
Last updated: May 03 2026 at 22:13 UTC