Stream: git-wasmtime

Topic: wasmtime / issue #4343 Note that epoch-interrupts are saf...


view this post on Zulip Wasmtime GitHub notifications bot (Jun 28 2022 at 03:06):

github-actions[bot] commented on issue #4343:

Subscribe to Label Action

cc @peterhuene

<details>
This issue or pull request has been labeled: "wasmtime:api", "wasmtime:config"

Thus the following users have been cc'd because of the following labels:

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

view this post on Zulip Wasmtime GitHub notifications bot (Jun 28 2022 at 03:06):

github-actions[bot] commented on issue #4343:

Label Messager: wasmtime:config

It looks like you are changing Wasmtime's configuration options. Make sure to
complete this check list:

[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.

Learn more.

</details>

view this post on Zulip Wasmtime GitHub notifications bot (Jun 28 2022 at 14:49):

alexcrichton commented on issue #4343:

Thanks for this! Instead of specifying exact details though could this instead be reworded to say that wasm code is guaranteed to check the epoch? I think it's definitely worthwhile to mention this but we may tweak the implementation over time but we'll always have the guarantee that no matter what the wasm does it will eventually check the epoch.


Last updated: Dec 23 2024 at 13:07 UTC