Skip to content

Conversation

@fitzgen
Copy link
Member

@fitzgen fitzgen commented Jan 8, 2026

Builds on top of #12296

Turns out we need to either do this migration or enable the wasmtime-internal-error crate's anyhow feature to convert winch compilation errors in wasmtime-internal-winch. This migration is preferable because we can avoid an anyhow dependency.

fitzgen added 15 commits January 8, 2026 11:24
When doing plain old `cargo test -p wiggle` (or `wiggle-test`) the test would
fail due to linking errors because Wasmtime's `std` cargo feature (and maybe
others) wasn't being enabled. The crate's tests would pass when run as part of
the whole workspace, however, because of cargo feature resolution and other
crates that enabled the necessary features, which is why CI is green.
This is another interesting one because wasi-common is used internally to
Wasmtime but also by other projects. Therefore, rather than using
`wastime::error::*` and making `wasmtime` a hard dependency, we use just
`wasmtime_environ::error`.
We are trying to switch to `format_err!` instead.
@fitzgen fitzgen requested review from a team as code owners January 8, 2026 21:54
@fitzgen fitzgen requested review from cfallin and dicej and removed request for a team January 8, 2026 21:54
@github-actions github-actions bot added the wasi Issues pertaining to WASI label Jan 8, 2026
@fitzgen fitzgen added this pull request to the merge queue Jan 9, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wasi Issues pertaining to WASI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants