feat: update wasi:config support to v0.2.0-rc.1 (#11978)

This commit updates wasi-config to the newly released
`wasi:[email protected]`, and dropping support for 0.2.0-draft.

feat: begin wasip3 implementation (#11221)

* ci: add subdir support

Signed-off-by: Roman Volosatovs <[email protected]>

* feat: extract common `WasiCtxBuilder`

Signed-off-by: Roman Volosatov

feat: begin wasip3 implementation (#11221)

* ci: add subdir support

Signed-off-by: Roman Volosatovs <[email protected]>

* feat: extract common `WasiCtxBuilder`

Signed-off-by: Roman Volosatovs <[email protected]>

* chore: vendor p3 WIT

Signed-off-by: Roman Volosatovs <[email protected]>

* feat: begin wasip3 implementation

Signed-off-by: Roman Volosatovs <[email protected]>

* chore(wasip3): remove now-redundant async stubs

Signed-off-by: Roman Volosatovs <[email protected]>

* test(wasip3): link wasip2

Signed-off-by: Roman Volosatovs <[email protected]>

* refactor: `allow` -> `expect`

Signed-off-by: Roman Volosatovs <[email protected]>

* chore: add bindgen `tracing` issue ref

ref https://github.com/bytecodealliance/wasmtime/issues/11245

Signed-off-by: Roman Volosatovs <[email protected]>

* chore: adapt to `Accessor` API changes

- hide `CommandPre`, since it is currently unusable
https://github.com/bytecodealliance/wasmtime/issues/11249
- use `Command::new` directly in examples, since `instantiate_async`
does not provide a way to call an export

Signed-off-by: Roman Volosatovs <[email protected]>

* doc: add a link to p3 `add_to_linker`

Signed-off-by: Roman Volosatovs <[email protected]>

---------

Signed-off-by: Roman Volosatovs <[email protected]>

show more ...

add Component Model async ABI tests (#11136)

* add Component Model async ABI tests

This pulls in the tests from the `wasip3-prototyping` repo, minus the ones
requiring WASIp3 support in `wasmtime-w

add Component Model async ABI tests (#11136)

* add Component Model async ABI tests

This pulls in the tests from the `wasip3-prototyping` repo, minus the ones
requiring WASIp3 support in `wasmtime-wasi[-http]`, which will be PR'd
separately.

* add audits and exemptions for new `component-async-tests` deps

In order to convince `cargo vet` that we only needed these deps to be
`safe-to-run` (not necessarily `safe-to-deploy`, since it's test code), I've
moved the `wasm-compose` dep to the `dev-dependencies` section of the
`Cargo.toml` file, which required rearranging some code.

I've exempted `wasm-compose` since it's a BA project, and also exempted all but
one of the remaining new deps since they each get well over 10,000 downloads per
day from crates.io. I've audited and certified the remaining dep, `im-rc`,
which came in a bit shy of the 10,000-per-day mark.

Signed-off-by: Joel Dice <[email protected]>

* simplify `component_async_tests::util::sleep`

Signed-off-by: Joel Dice <[email protected]>

---------

Signed-off-by: Joel Dice <[email protected]>

show more ...

Update to WASI 0.2.6. (#11049)

* Update to WASI 0.2.6.

This includes two changes:

# https://github.com/WebAssembly/wasi-filesystem/pull/165
Documentation update

# https://github.com/WebAssembly/w

Update to WASI 0.2.6. (#11049)

* Update to WASI 0.2.6.

This includes two changes:

# https://github.com/WebAssembly/wasi-filesystem/pull/165
Documentation update

# https://github.com/WebAssembly/wasi-http/pull/139
Adds a new unstable `send-informational` function to the `response-outparam` resource. I've left this `unimplemented!()`.

* Trap instead of panic

show more ...

Expose Wasi-TLS handshake error (#10429)

* Expose TLS errors to the guest.

* Add a test to check the non-happy flow and verify that the error is properly propagated into the guest.

* Update WIT ve

Expose Wasi-TLS handshake error (#10429)

* Expose TLS errors to the guest.

* Add a test to check the non-happy flow and verify that the error is properly propagated into the guest.

* Update WIT versions

show more ...

Vendor wasi-tls wits (#10392)

* Setup the WIT folder structure and CI check similar to how its done for other proposals.

* Add wasi-tls to list of proposals

* Fix whitespace

Initial implementation of Wasi-tls (Transport Layer Security) (#10249)

* Initial implementation of wasi-tls

This crate provides the Wasmtime host implementation for the [wasi-tls] API.
The [wasi-t

Initial implementation of Wasi-tls (Transport Layer Security) (#10249)

* Initial implementation of wasi-tls

This crate provides the Wasmtime host implementation for the [wasi-tls] API.
The [wasi-tls] world allows WebAssembly modules to perform SSL/TLS operations,
such as establishing secure connections to servers. TLS often relies on other wasi networking systems
to provide the stream so it will be common to enable the [wasi:cli] world as well with the networking features enabled.

The initial implemntation is using rustls.

Signed-off-by: James Sturtevant <[email protected]>

* Remove configuration object for now

Signed-off-by: James Sturtevant <[email protected]>

* Update cargo patch to use temp branch

Signed-off-by: James Sturtevant <[email protected]>

* Rename tcp streams to wasistreams to be more generic

Signed-off-by: James Sturtevant <[email protected]>

* gate the wasi-tls ctx behind a feature

Signed-off-by: James Sturtevant <[email protected]>

* cleanup and clippy fixes

Signed-off-by: James Sturtevant <[email protected]>

* Fix issue when another pollable cancels

Signed-off-by: James Sturtevant <[email protected]>

* prtest:full

Signed-off-by: James Sturtevant <[email protected]>

* Skip test on riscv64/s390x

Signed-off-by: James Sturtevant <[email protected]>

* Drop debug info to support tests on pulley based platforms

Signed-off-by: James Sturtevant <[email protected]>

* Update signature of `close-notify`

* Use draft version

Signed-off-by: James Sturtevant <[email protected]>

* Remove patches

Signed-off-by: James Sturtevant <[email protected]>

* Ungate tls on riscv64 and s390x

* Un-gate wais-http on riscv64/s390x as well

* Add wasmtime-wasi-tls to publish list

* Add wasmtime-wasi-tls to public API crate list

* Revert some changes to Cargo.lock

---------

Signed-off-by: James Sturtevant <[email protected]>
Signed-off-by: James Sturtevant <[email protected]>
Co-authored-by: badeend <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>

show more ...

Update to WASI 0.2.3 WIT files (#9807)

* Update to WASI 0.2.3 WIT files

No major changes here; this just updates WIT files from WASI 0.2.2 to 0.2.3.

* Update the vendor-wit.sh script to 0.2.3.

Rename wasi-runtime-config to wasi-config (#9404)

* Rename wasi-runtime-config to wasi-config

* Remove audit-as-cratesio entry

This crate no longer exists on crates.io so cargo-vet is failing

---

Rename wasi-runtime-config to wasi-config (#9404)

* Rename wasi-runtime-config to wasi-config

* Remove audit-as-cratesio entry

This crate no longer exists on crates.io so cargo-vet is failing

---------

Co-authored-by: Alex Crichton <[email protected]>

show more ...

Update WASI WITs to 0.2.2 (#9395)

* Update WASI WITs to 0.2.2

This bumps a number of versions in a number of locations and will be
slated for Wasmtime 27. This additionally requires implementing th

Update WASI WITs to 0.2.2 (#9395)

* Update WASI WITs to 0.2.2

This bumps a number of versions in a number of locations and will be
slated for Wasmtime 27. This additionally requires implementing the
`network-error-code` function which I've left as a stub for now to get
filled out with tests at a later date.

* Fix doc examples

show more ...

Configure WIT feature gates at runtime & implement wasi-cli `exit-with-code` (#9381)

* Remove `features` configuration from component::bindgen! and always emit all unstable members. These features w

Configure WIT feature gates at runtime & implement wasi-cli `exit-with-code` (#9381)

* Remove `features` configuration from component::bindgen! and always emit all unstable members. These features will be gated at runtime.

* Implement wasi-cli's unstable `exit-with-code`

* Add codegen test for unstable features

* Add LinkOptions type and add a parameter to all add_to_linker functions in for worlds/interfaces that use any unstable feature.

* More descriptive test feature names.

* Generate feature gate `if` checks

* Expose `cli-exit-with-code` as CLI option

* Generate bespoke option types per interface and world.

* Add unit test

* Remove exit code restriction on Windows

* Add cli_exit_with_code test

* Use BTreeSet to generate the options in consistent order

* Change wasmtime-wasi's `add_to_linker_(a)sync` signature back to how it was and add new variants that take the option parameters.

* Lift Windows exit code restriction in tests

* Lift Windows exit code restriction

show more ...

test-programs: use the wasi:http/imports world (#9111)

test-programs: reorganize wasi content generated by wit and remove unnecessary deps (#9080)

Update to WASI WITs 0.2.1 (#9063)

No major changes happen in this release so it's just bumping version
numbers. The goal here is to turn the crank and ensure that nothing else
breaks as part of this

Update to WASI WITs 0.2.1 (#9063)

No major changes happen in this release so it's just bumping version
numbers. The goal here is to turn the crank and ensure that nothing else
breaks as part of this release process. There's a surprising number of
versions to update in-repo which we may want to make easier in the
future but for now this just manually updates.

It is planned that this does not actually break anyone in practice.
Older runtimes should support newer versions and Wasmtime after this PR
should continue to support older binaries as well.

Put another way this should not break things and if it does this will
get reverted and fixed. We've done our best to make sure this won't
break things, so let's find out in the real world now.

show more ...

Implement wasi-keyvalue (#8983)

* Implement wasi-keyvalue

* Allow preset data for In-Memory provider, rename allow_hosts to allow_redis_hosts

* Add vets

---------

Co-authored-by: Alex Crichton <

Implement wasi-keyvalue (#8983)

* Implement wasi-keyvalue

* Allow preset data for In-Memory provider, rename allow_hosts to allow_redis_hosts

* Add vets

---------

Co-authored-by: Alex Crichton <[email protected]>

show more ...

Implement wasi-runtime-config (#8950)

* Implement wasi-runtime-config

* Avoid clone the WasiRuntimeConfig every time

Update dependency on `wit-bindgen` (#8911)

* Update dependency on `wit-bindgen`

Updating to the latest released version.

* Add vets

* Fix build of test-programs

wasi-nn: factor out common test-program code (#8522)

`wasi-nn`'s test program suite is light at the moment but, in order to
expand it, this change factors out some of the common bits that are
being

wasi-nn: factor out common test-program code (#8522)

`wasi-nn`'s test program suite is light at the moment but, in order to
expand it, this change factors out some of the common bits that are
being used in the `test-programs` crate. Since all of the tests perform
some kind of image classification, the new `nn` module gains `classify`
and `sort_results` functions to help with this exact case.

prtest:full

show more ...

Support dirs/env vars in `wasmtime serve` (#8279)

* More flags like `--dir` and `--env` are moved into `RunCommon` to be
shared between `wasmtime serve` and `wasmtime run`, meaning that the
`ser

Support dirs/env vars in `wasmtime serve` (#8279)

* More flags like `--dir` and `--env` are moved into `RunCommon` to be
shared between `wasmtime serve` and `wasmtime run`, meaning that the
`serve` command can now configure environment variables.

* A small test has been added as well as infrastructure for running
tests with `wasmtime serve` itself. Previously there were no tests
that executed `wasmtime serve`.

* The `test_programs` crate had a small refactoring to avoid
double-generation of http bindings.

show more ...

Refactor the test-programs test suite (#7182)

* Refactor the test-programs test suite

This commit is a large refactoring that reorganizes `test-programs` and
how we tests wasms in Wasmtime. Often w

Refactor the test-programs test suite (#7182)

* Refactor the test-programs test suite

This commit is a large refactoring that reorganizes `test-programs` and
how we tests wasms in Wasmtime. Often writing tests requires complicated
interactions with the guest which can't be done via hand-written `*.wat`
syntax and requires a compiler to get engaged. For this purpose Wasmtime
currently has the `crates/test-programs/*` test suite which builds files
from source and then runs the tests. This has been somewhat cumbersome
in the past though and it's not been easy to extend this over time, so
this commit attempts to address this.

The scheme implemented in this PR looks like:

* All wasm test programs live in `crates/test-programs/src/bin/*.rs`.
All of them, no exceptions.

* Wasm tests have shared support located at
`crates/test-programs/src/lib.rs` and its submodules, such as bindings
generation for WASI.

* Wasm tests are built by a new `crates/test-programs/artifacts` crate.
This crate compiles modules and additionally creates components for
all test programs. The crate itself only records the path to these
outputs and a small amount of testing support, but otherwise doesn't
interact with `wasmtime`-the-crate itself.

* All tests in `crates/test-programs/tests/*.rs` have moved. For example
wasi-http tests now live at `crates/wasi-http/tests/*.rs`. Legacy
tests of wasi-common now live at `crates/wasi-common/tests/*.rs`.
Modern tests for preview2 live at `crates/wasi/tests/*.rs`.

* Wasm tests are bucketed based on their filename prefix. For example
`preview1_*` is tested in wasi-common and wasmtime-wasi. The
`preview2_*` prefix is only tested with wasmtime-wasi, however.

* A new `cli_*` prefix is used to execute tests as part of
`tests/all/main.rs`. This is a new submodule in
`tests/all/cli_tests.rs` which executes these components on the
command line. Many old "command" tests were migrated here.

* Helper macros are generated to assert that a test suite is run in its
entirety. This way if a `preview1_*` test is added it's asserted to
get added to both wasi-common and wasmtime-wasi in the various modes
they run tests.

Overall this moved a number of tests around and refactored some edges of
the tests, but this should not lose any tests (except one that wasn't
actually testing anything). Additionally the hope is that it's much
easier to add tests in the future. The process is to add a new file in
`crates/test-programs/src/bin/*.rs` named appropriately. For example a
preview2 executable is `preview2_*` and a CLI tests is `cli_*`. When
building the test suite an error is generated in the appropriate module
then of "please write a test here", and then a test is written in the
same manner as the other tests in the module.

* Remove no-longer-needed fetches

prtest:full

* I'm worried wasi is running low on semicolons

* Add the WASI target in all CI actions

* Add unknown-unknown target on all CI builders too

* Fix building test artifacts under miri

Need to avoid wrappers for these cross-compiled targets

* Break circular dependency for packaging

Don't use the workspace dep for `wasmtime-wasi` since it injects a
version, instead use a `path = '..'` dependency to fool Cargo into
dropping the dependency during the package phase.

* Fix some merge conflicts with tests

* Fix rebase for new tests

* Remove stray comment

* Fix some flaky tests

* Fix network tests in synchronous mode

This commit is an attempt to fix some networking tests in synchronous
mode in our test suite. Currently networking tests don't actually run in
synchronous mode on CI which is why no failures have been surfaced yet,
but the refactoring in #7182 is going to start doing this.

Currently the `udp_sample_application.rs` test blocks infinitely in
synchronous mode for me locally, most of the time. This appears to be an
interaction between how Tokio handles readiness and how we're
entering the event loop. We're effectively entering the Tokio event loop
with a future that's always ready which ends up starving Tokio of
otherwise performing its background work such as updating flags for
readiness of reading/writing.

The fix here is to add a yield at the start of an `in_tokio` block which
is used in synchronous mode. This is a kludge fix but the intention is
to enable Tokio to have a chance to update readiness flags and process
events from epoll/kqueue/etc.

An additional fix to this issue is WebAssembly/wasi-sockets#64 where the
test is waiting on `READABLE` or `WRITABLE`, but in this specific case
it should only wait on `READABLE`. If it waited on just this then that
would also fix this issue. Nevertheless having a `yield_now` is expected
to have little-to-no overhead and otherwise fix this edge case of an
always-ready future.

* Fix passing empty arguments on the CLI

* Add another blocking accept

* Update crates/test-programs/src/bin/api_proxy.rs

Co-authored-by: Trevor Elliott <[email protected]>

---------

Co-authored-by: Trevor Elliott <[email protected]>

show more ...

Remove usage of `is-terminal` and `atty` crates (#7104)

* Remove usage of `is-terminal` and `atty` crates

This functionality is now folded into the standard library itself.

* Fix syntax

* Fix a u

Remove usage of `is-terminal` and `atty` crates (#7104)

* Remove usage of `is-terminal` and `atty` crates

This functionality is now folded into the standard library itself.

* Fix syntax

* Fix a unix/windows cfg

show more ...

feat: align wasi-http with component linker (#6195)

* feat: align wasi-http with component linker

* feat(wasi-http): allow bidirectional stream

* feat(wasi-http): clean up children when dropping r

feat: align wasi-http with component linker (#6195)

* feat: align wasi-http with component linker

* feat(wasi-http): allow bidirectional stream

* feat(wasi-http): clean up children when dropping resource

* chore: update based on feedback

* chore: replace wasi http context references

* chore: fix logical issue with outgoing body stream

* chore: use thread-safe reference-counting pointer

* chore: cleanup resources using table

* fix(wasi-preview1-component-adapter): sync command extended wit

* fix(wasi-preview1-component-adapter): sync command extended wit

* fix(wasmtime-wasi): sync wit for http types

* chore: refactor using wasmtime-wasi crate

fix(wasi-http): misconfiguration in wasmtime linkers

chore: keep streams details

chore: fix wasi http tests

* chore: use pollable from wasmtime-wasi

* chore: update wasi http linker for module

* chore: update test programs for wasi http

* fix(wasi-http): ensure proper errors are surfaced

* chore: split wasi http tests into individual files

* chore: ensure protocol error is mapped correctly

* chore: disable temporarily wasi http in wasmtime cli

* chore: comment out wasi http in wasmtime cli

* chore(ci): ensure wit definitions in sync

* feat(wasi-http): generate async host binding

* chore: make wasi http tests async

* chore: update ci workflow based on suggestion

Co-authored-by: Pat Hickey <[email protected]>

* feat(wasmtime-wasi): update logging world to latest

* feat(wasmtime): update proxy world to latest

* feat(wasmtime-wasi): add back command extended world

* fix(wasi-http): sync wit definitions

* chore: update tests with latest wit definitions

* Update src/commands/run.rs

* Update src/commands/run.rs

* Update src/commands/run.rs

* Update src/commands/run.rs

* Update src/commands/run.rs

* Update src/commands/run.rs

* Update src/commands/run.rs

* Update src/commands/run.rs

* Update src/commands/run.rs

* chore: fix formatting

* Ignore flaky test

* chore: fix compilation error for riscv64 arch

* Avoid `cp -T` on macos

Adding prtest:full to ensure that we've seen a successful build before
queuing.

* Don't build the wasi-http test programs for the native target

* Debug the wit consistency check

* Update streams.wit in wasi-http

* Mark the component outbound_request_post test flaky

* Disable flaky wasi-http-tests on windows only

* Use diff instead of rm/cp/git diff

* Disable more tests on windows

---------

Co-authored-by: Eduardo Rodrigues <[email protected]>
Co-authored-by: Pat Hickey <[email protected]>
Co-authored-by: Trevor Elliott <[email protected]>

show more ...

Sync wasi-cli with wit definitions in standards repo (#6806)

* rename wasi-cli-base to wasi-cli, delete `preview` package, import wasi-cli

wasi-cli import is sum of
https://github.com/WebAssembly/

Sync wasi-cli with wit definitions in standards repo (#6806)

* rename wasi-cli-base to wasi-cli, delete `preview` package, import wasi-cli

wasi-cli import is sum of
https://github.com/WebAssembly/wasi-cli/pull/19 and
https://github.com/WebAssembly/wasi-cli/pull/20

* wasi impl: change bindgen arguments and mod paths from cli_base to cli

* correct name of wasi-cli deps dir to just `deps/cli/`

it turns out this isnt semantically meaningful, since the package name
is in the document itself now, but lets be consistient

* track whether stdio isatty in ctx, and impl the cli/terminal-* interfaces

* rebase fixup

* wasi wits: define the reactor adapter's world

* component adapter: fixes

* test-programs/command-tests: fix renaming cli_base to cli

* component adapter: fix manually-defined export and import names

* test harness fixes

* preview1 component adapter: fill in isatty detection

* implement isatty in preview2-to-preview1 host adapter

* test-programs: cover both when stdio isatty and not

prtest:full

* split isatty test for regular file and stdio, detect host stdio is_terminal

CI environments vary - let the test runner make sure the host process's
stdio is in fact a terminal before asserting that the guest sees it is a
terminal.

* provide an is-terminal impl for all preview2's stdio types

which means making a newtype around Stdout and Stderr instead of using
a type alias there.

and then use the is-terminal impl to fill in the isatty field in the
builder when inheriting. if you need to override it you can always
builder.stdin(stdio::stdin(), your_own_idea_of_isatty)

* finally, rename IsATTY variants to Yes and No

* Fix the reference to IsATTY::No

* more forgotten renamings

---------

Co-authored-by: Trevor Elliott <[email protected]>

show more ...

factor out common config to test-programs crate

Reorganize wasi-misc-tests. (#575)

* Reorganize wasi-misc-tests.

Move wasi-misc-tests out of wasi-common, to break a dependency cycle;
previously, wasmtime-* depended on wasi-common, but wasi-co

Reorganize wasi-misc-tests. (#575)

* Reorganize wasi-misc-tests.

Move wasi-misc-tests out of wasi-common, to break a dependency cycle;
previously, wasmtime-* depended on wasi-common, but wasi-common
dev-dependended on wasmtime-*.

Now, wasi-common no longer dev-depends on wasmtime-*; instead, the
tests are in their own crate which depends on wasi-common and on
wasmtime-*.

Also, rename wasi-misc-tests to wasi-tests for simplicity.

This also removes the "wasm_tests" feature; it's replaced by the
"test-programs" feature.

* Update the CI script to use the new feature name.

* Update the CI script to use the new feature name in one more place.

* Change a `write!` to a `writeln!`.

show more ...