Stream: git-wasmtime

Topic: wasmtime / PR #10235 Update wasm-tools crates to 226

Wasmtime GitHub notifications bot (Feb 14 2025 at 21:06):

alexcrichton opened PR #10235 from alexcrichton:update-wasm-tools to bytecodealliance:main:

This commit updates the wasm-tools crates to the 226 track of versions. The most notable change here is the removal and refactoring within wasm-tools of support for multiple and named returns in the component model along with the support for 33+ flags in the flags type. This has been gated for some time now and it's just now being removed now that it's been awhile an no issues have been raised.

<!--
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.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

Wasmtime GitHub notifications bot (Feb 14 2025 at 21:07):

alexcrichton commented on PR #10235:

I'll note that this is a draft because I haven't actually published anything yet on the wasm-tools side of things.

Wasmtime GitHub notifications bot (Feb 14 2025 at 22:44):

github-actions[bot] commented on PR #10235:

Subscribe to Label Action

cc @fitzgen

<details>
This issue or pull request has been labeled: "fuzzing", "wasmtime: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 (Feb 14 2025 at 23:45):

github-actions[bot] commented on PR #10235:

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 Config method, 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 Config method, 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 nested structs).

  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.

Learn more.

</details>

Wasmtime GitHub notifications bot (Feb 17 2025 at 12:17):

alexcrichton updated PR #10235.

Wasmtime GitHub notifications bot (Feb 17 2025 at 12:43):

alexcrichton updated PR #10235.

Wasmtime GitHub notifications bot (Feb 19 2025 at 19:16):

alexcrichton updated PR #10235.

Wasmtime GitHub notifications bot (Feb 19 2025 at 19:17):

alexcrichton has marked PR #10235 as ready for review.

Wasmtime GitHub notifications bot (Feb 19 2025 at 19:17):

alexcrichton requested wasmtime-fuzz-reviewers for a review on PR #10235.

Wasmtime GitHub notifications bot (Feb 19 2025 at 19:17):

alexcrichton requested wasmtime-core-reviewers for a review on PR #10235.

Wasmtime GitHub notifications bot (Feb 19 2025 at 19:17):

alexcrichton requested dicej for a review on PR #10235.

Wasmtime GitHub notifications bot (Feb 19 2025 at 19:17):

alexcrichton requested wasmtime-default-reviewers for a review on PR #10235.

Wasmtime GitHub notifications bot (Feb 19 2025 at 19:17):

alexcrichton commented on PR #10235:

Ok should be ready to go now.

Wasmtime GitHub notifications bot (Feb 19 2025 at 19:28):

pchickey submitted PR review.

Wasmtime GitHub notifications bot (Feb 19 2025 at 20:58):

alexcrichton merged PR #10235.

Last updated: Feb 28 2025 at 02:27 UTC