Stream: git-wasmtime

Topic: wasmtime / PR #8127 [19.0.0] Fix `wasmtime settings` comm...

Wasmtime GitHub notifications bot (Mar 14 2024 at 00:18):

alexcrichton opened PR #8127 from alexcrichton:release-19.0.0-backport to bytecodealliance:release-19.0.0:

Backport of #8060 to the 19.0.0 release branch

Wasmtime GitHub notifications bot (Mar 14 2024 at 00:18):

alexcrichton requested fitzgen for a review on PR #8127.

Wasmtime GitHub notifications bot (Mar 14 2024 at 00:18):

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

Wasmtime GitHub notifications bot (Mar 14 2024 at 01:03):

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

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:

• peterhuene: wasmtime:api

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 (Mar 14 2024 at 01:03):

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

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 (Mar 14 2024 at 13:49):

fitzgen submitted PR review.

Wasmtime GitHub notifications bot (Mar 14 2024 at 14:13):

alexcrichton merged PR #8127.

Last updated: Nov 22 2024 at 17:03 UTC