Wasmtime GitHub notifications bot (Oct 21 2025 at 22:50): Wasmtime GitHub notifications bot (Oct 21 2025 at 22:50):saulecabrera opened PR #11904 from saulecabrera:update-strategy-docs to bytecodealliance:main:
To reflect the current state of affairs regarding Winch development.
<!--
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 (Oct 21 2025 at 22:50):saulecabrera requested wasmtime-core-reviewers for a review on PR #11904.
Wasmtime GitHub notifications bot (Oct 21 2025 at 22:50):saulecabrera requested pchickey for a review on PR #11904.
Wasmtime GitHub notifications bot (Oct 21 2025 at 22:54):alexcrichton submitted PR review.
Wasmtime GitHub notifications bot (Oct 21 2025 at 22:54):alexcrichton has enabled auto merge for PR #11904.
Wasmtime GitHub notifications bot (Oct 22 2025 at 02:18):github-actions[bot] commented on PR #11904:
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 (Oct 22 2025 at 11:52):saulecabrera commented on PR #11904:
The failure is coming from https://github.com/bytecodealliance/wasmtime/actions/runs/18704110053/job/53338648482, which is (I think) the same symptom for all the other, recent PRs that have been removed from the queue.
Wasmtime GitHub notifications bot (Oct 22 2025 at 14:59):alexcrichton commented on PR #11904:
I've attempted a fix for that over at https://github.com/bytecodealliance/wasmtime/pull/11907
Wasmtime GitHub notifications bot (Oct 22 2025 at 15:26):saulecabrera commented on PR #11904:
Reviewed, thanks Alex!
Wasmtime GitHub notifications bot (Oct 22 2025 at 15:52):alexcrichton merged PR #11904.
Last updated: Dec 06 2025 at 07:03 UTC