Wasmtime GitHub notifications bot (Oct 30 2026 at 16:05): Wasmtime GitHub notifications bot (Oct 30 2026 at 16:05):alexcrichton opened PR #15091 from alexcrichton:document-imprecise-fuel-consumption-on-trap to bytecodealliance:main:
The implementation of fuel right now does not maintain a precise count of fuel consumed in the event that WebAssembly traps. For example fuel is not flushed back to the store before a division instruction which may trap, or any load/store instruction. This change ensures that this is at least documented on
Config::consume_fuelto ensure it's a known property of fuel.<!--
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 review the Bytecode Alliance's AI tool usage policy at
https://github.com/bytecodealliance/governance/blob/main/AI_TOOL_POLICY.mdPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Oct 30 2026 at 16:05):alexcrichton requested cfallin for a review on PR #15091.
Wasmtime GitHub notifications bot (Oct 30 2026 at 16:05):alexcrichton removed the review request for wasmtime-core-reviewers from PR #15091.
Wasmtime GitHub notifications bot (Oct 30 2026 at 16:05):alexcrichton requested wasmtime-core-reviewers for a review on PR #15091.
Wasmtime GitHub notifications bot (Oct 30 2026 at 18:44):github-actions[bot] added the label wasmtime:api on PR #15091.
Wasmtime GitHub notifications bot (Oct 30 2026 at 18:44):github-actions[bot] added the label wasmtime:config on PR #15091.
Wasmtime GitHub notifications bot (Oct 30 2026 at 19:45):github-actions[bot] commented on PR #15091:
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 31 2026 at 23:03 UTC