Changes in Cargo.toml

133a0ef4 - Debugging: add the debug-main world. (#12756)

Fri, 13 Mar 2026 18:58:17 +0000

Debugging: add the debug-main world. (#12756)* Debugging: add the debug-main world.This PR "draws the rest of the owl" for the debug-mainworld (bytecodealliance/rfcs#45). This includes a WIT world that hostsdebug components that have access to "host debug powers" via adebugging API, and the ability to load such a debug-component and giveit control of the main program as a debuggee when using `wasmtimerun`.The WIT is namespaced to `bytecodealliance:wasmtime` and is slightlyaspirational in places: for example, the host does not yet implementinjection of early return values or exception-throws. I intend to fillout a series of TODO issues once this all lands to track followup("post-MVP") work.This PR does not include any debug components. I separately have agdbstub component, with which I tested and co-developed this host-sideimplementation. My plan is to land it in a followup PR as a componentthat will be embedded in/shipped with the Wasmtime CLI and availableunder an easy-to-use CLI option. Once we have that gdbstub component,we can also implement end-to-end integration tests that boot up LLDBand run through an expected interaction. (Separately, thoseintegration tests will require a release of wasi-sdk to ship an LLDBbinary that we can use.) As such, there are no real tests in this PR:interesting behaviors only really occur with a full end-to-end flow.The integration with the CLI is a little awkward (we internally buildanother `wasmtime run` command that invokes the debug component, andtie it together with the debuggee via a special `invoke_debugger` API;this seemed less bad than reworking all of the WASI setup to be morereusable). Happy to take more ideas here.* Review feedback.* Review feedback.* Review feedback: update vendor-wit.sh.* Review feedback: -Ddebugger-arg= -> -Darg=.* Review feedback.* Review feedback.* Review feedback: factor host.rs into several submodules.* Review feedback: rename Debugger to Debuggee on host side.* Review feedback: split inherit_stdin_stdout, and add corresponding options for the debug component.* Review feedback.* Review feedback.* Add simple debug-component tests.* Add wasm32-wasip2 target in a few places in CI* Cargo vets for wstd dependency.* Add wasm32-wasip2 in more places* fix debug-component test dependence on componentization byte offsets* Review feedback.* Fix cancel-safety of EventFuture.* Fix: Interrupted events should only occur after interrupt(), not on every epoch yield.* Review feedback.* Review feedback: strip down WASI imports in debugger world.* fold debugger test component back into wasip1 + adapter test artifact compilation flow List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

b298f375 - RR #2: Sha256 checksum for components (#12576)

Fri, 13 Feb 2026 21:11:58 +0000

RR #2: Sha256 checksum for components (#12576)* Add sha256 checksum for component for record/replay consistency* Move sha2 crate as workspace dependency* Run checksum digest only on recording configs* Fix CI error and restructure from_binary List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

fee9be21 - Add a new fuzzer focused on component-model-async events (#12119)

Tue, 09 Dec 2025 19:32:20 +0000

Add a new fuzzer focused on component-model-async events (#12119)* Add a new fuzzer focused on component-model-async eventsThis commit adds a new fuzzer mode to the `misc` fuzzer of Wasmtimewhich is focused on async events and interleavings of components usingthe component-model-async proposal. This fuzzer works by having aprecompiled guest program which serves as the component to run. Thisprecompiled component has a custom `fuzz.wit` which is used to interfacewith the fuzzer itself. The fuzzer is then a fuzz-generated sequence ofcommands to send to the component which verifies that everythingexecutes correctly, has no panics, etc.This fuzzer intends to stress async communication and taskinfrastructure with component-model-async. Notably this does not stresslifting/lowering or arbitrary type signatures. This does, however,permute all of the following:* Guest/host interactions (also guest/guest, host/host, etc).* Async functions, both ready and pending.* Future operations: reads, writes, cancellation, transfers, etc.* Stream operations: reads, writes, cancellation, transfers, etc.This is all throwing into a large "soup" and then asserted to workcorrectly. There's a few gotchas here and there for how this fuzzer isdesigned, such as some events requiring "yield N times to await thisevent happening". This is required because Wasmtime is allowed tonon-deterministically select between a number of "ready events" and whatto dispatch.This is not intended to be a one-size-fits-all fuzzer forcomponent-model-async. The recent enhancements to the `component_api`fuzzer are intended to complement this fuzzer in terms of what'sstressed where internally.* Review comments List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

69ef9afc - Update to using `wasip1`-the-crate (#12131)

Fri, 05 Dec 2025 22:13:42 +0000

Update to using `wasip1`-the-crate (#12131)Switch away from `wasi`, which while it isn't changing might as well beexplicit. List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

020727d0 - Update wasm-tools dependencies (#12031)

Fri, 14 Nov 2025 21:34:45 +0000

Update wasm-tools dependencies (#12031)* Change separator style* Update wasm-tools dependencies* Also update wit-bindgen* Drop `[async]` name prefixes* Plumb `async` as part of a function typeRuntime handling of async functions and new traps are to be implementedin subsequent commits. This is just getting everything running again.* Run clang-format, also add test* Fix some more wast tests---------Co-authored-by: Sy Brand List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

bbea2c46 - Use `wasip{1,2}` crates, not `wasi` (#11673)

Wed, 10 Sep 2025 22:22:12 +0000

Use `wasip{1,2}` crates, not `wasi` (#11673)These are the new structure for how the `wasi-rs` repository is managed. List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

1047b511 - Update wit-bindgen to 0.45.0 (#11609)

Thu, 04 Sep 2025 23:19:56 +0000

Update wit-bindgen to 0.45.0 (#11609)* Update wit-bindgen to 0.45.0Pulling in recent changes* Add vets* Remove dead imports List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

804060c8 - add Component Model async ABI tests (#11136)

Fri, 11 Jul 2025 23:32:19 +0000

add Component Model async ABI tests (#11136)* add Component Model async ABI testsThis pulls in the tests from the `wasip3-prototyping` repo, minus the onesrequiring WASIp3 support in `wasmtime-wasi[-http]`, which will be PR'dseparately.* add audits and exemptions for new `component-async-tests` depsIn 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'vemoved 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 butone of the remaining new deps since they each get well over 10,000 downloads perday 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 * simplify `component_async_tests::util::sleep`Signed-off-by: Joel Dice ---------Signed-off-by: Joel Dice List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

8e883429 - Update some dependencies on their major version tracks (#10425)

Thu, 20 Mar 2025 01:40:14 +0000

Update some dependencies on their major version tracks (#10425)* Update rustix to 1.0.x* Bump itertools to its latest version* Update base64 to its latest version* Update wit-bindgen to its latest version* Update v8 to its latest version on crates.ioJust keeping up-to-date* Update capstone dependency to its latest version* Update libtest-mimic to its latest version* Update cargo-metadata dependency* Update thiserror dependency to latest* Update bytesize dependency* Drop getrandom dependency from test-programsFavor using `wasi::random_get` instead for now.* Fix deny.toml syntax* Fix merge conflict* Downgrade v8 to respect MSRV* Fix compile on windows List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

953adeed - Rename `wasi` crate to `wasip1` in test-programs (#10426)

Wed, 19 Mar 2025 21:01:24 +0000

Rename `wasi` crate to `wasip1` in test-programs (#10426)This better reflects how the test programs currently have access to bothversions, so make sure they're both named to disambiguate against theother. List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

7ba03476 - Fix a missing increment in p1-to-p2 adapter (#10064)

Tue, 21 Jan 2025 18:06:17 +0000

Fix a missing increment in p1-to-p2 adapter (#10064)This commit fixes a bug in the WASIp1-to-WASIp2 adapter during`fd_prestat_dir_name` where an iterator variable was forgotten to beincremented. That means that getting the path for anything other thanthe first preopen didn't work correctly.Closes #10058 List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

83029e3f - Add `rust-version.workspace = true` to all crates (#9112)

Mon, 12 Aug 2024 15:52:11 +0000

Add `rust-version.workspace = true` to all crates (#9112)Right now this is only on some crates such as `wasmtime` itself and`wasmtime-cli`, but by applying it to all crates it helps with versionselection of those using just Cranelift for example. List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

d8f7c77f - Start migrating some Wasmtime crates to no_std (#8463)

Thu, 25 Apr 2024 23:29:31 +0000

Start migrating some Wasmtime crates to no_std (#8463)* Start migrating some Wasmtime crates to no_stdThis commit is the first in what will be multiple PRs to migrateWasmtime to being compatible with `#![no_std]`. This work is outlinedin #8341 and the rough plan I have in mind is to go on a crate-by-cratebasis and use CI as a "ratchet" to ensure that `no_std` compat ispreserved. In that sense this PR is a bit of a template for future PRs.This PR migrates a few small crates to `no_std`, basically those thatneed no changes beyond simply adding the attribute. The nontrivial partsintroduced in this PR are:* CI is introduced to verify that a subset of crates can indeed be built on a `no_std` target. The target selected is `x86_64-unknown-none` which is known to not have `std` and will result in a build error if it's attempted to be used.* The `anyhow` crate, which `wasmtime-jit-icache-coherence` now depends on, has its `std` feature disabled by default in Wasmtime's workspace. This means that some crates which require `std` now need to explicitly enable the feature, but it means that by-default its usage is appropriate for `no_std`.The first point should provide CI checks that compatibility with`no_std` indeed works, at least from an "it compiles" perspective. Notethat it's not sufficient to test with a target like`x86_64-unknown-linux-gnu` because `extern crate std` will work on thattarget, even when `#![no_std]` is active.The second point however is likely to increase maintenance burdenin Wasmtime unfortunately. Namely we'll inevitably, either here or inthe future, forget to turn on some feature for some crate that's notcovered in CI checks. While I've tried to do my best here in covering itthere's no guarantee that everything will work and the combinatorialexplosion of what could be checked in CI can't all be added to CI.Instead we'll have to rely on bug fixes, users, and perhaps pointreleases to add more use cases to CI over time as we see fit.* Add another std feature* Another std feature* Enable anyhow/std for another crate* Activate `std` in more crates* Fix miri build* Fix compile on riscv64prtest:full* Fix min-platform example build* Fix icache-coherence again List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

54d3727a - wasi-nn: adapt to new test infrastructure (#7679)

Fri, 15 Dec 2023 23:22:55 +0000

wasi-nn: adapt to new test infrastructure (#7679)* wasi-nn: add test programsThis change adds new test programs for wasi-nn in a way fits in with theexisting WASI test infrastructure. The code is not new, though: thisreuses the wasi-nn `examples`, which are currently used by the`run-wasi-nn-example.sh` CI script. Eventually the examples will beremoved in favor of these tests.Because wasi-nn's component model support is still in flight, thischange also skips the generation of components for `nn_`-prefixed tests.* wasi-nn: add `testing` moduleThis testing-only module has code (i.e., `check_test!`) to check whetherOpenVINO and some test artifacts are available. The test artifacts aredownloaded and cached if not present, expecting `curl` to be present onthe command line (as discussed in the previous version of this, #6895).* wasi-nn: run `nn_*` test programs as integration testsFollowing the pattern of other WASI crates, this change adds thenecessary infrastructure to run the `nn_*` files in`crates/test-programs` (built by `test-program-artifacts`). These testsare only run when two sets of conditions are true:- statically: we only run these tests where we expect OpenVINO to be easy to install and run (e.g., the `cfg_attr` parts)- dynamically: we also only run these tests when the OpenVINO libraries can be located and the model artifacts can be downloaded* ci: install OpenVINO for running wasi-nn testsprtest:full* vet: certify the `wasi-nn` crate* ci: remove wasi-nn test script List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

5856590f - Configure workspace lints, enable running some Clippy lints on CI (#7561)

Mon, 20 Nov 2023 23:23:41 +0000

Configure workspace lints, enable running some Clippy lints on CI (#7561)* Configure Rust lints at the workspace levelThis commit adds necessary configuration knobs to have lints configuredat the workspace level in Wasmtime rather than the crate level. Thisuses a feature of Cargo first released with 1.74.0 (last week) of the`[workspace.lints]` table. This should help create a more consistent setof lints applied across all crates in our workspace in addition topossibly running select clippy lints on CI as well.* Move `unused_extern_crates` to the workspace levelThis commit configures a `deny` lint level for the`unused_extern_crates` lint to the workspace level rather than theprevious configuration at the individual crate level.* Move `trivial_numeric_casts` to workspace level* Change workspace lint levels to `warn`CI will ensure that these don't get checked into the codebase andotherwise provide fewer speed bumps for in-process development.* Move `unstable_features` lint to workspace level* Move `unused_import_braces` lint to workspace level* Start running Clippy on CIThis commit configures our CI to run `cargo clippy --workspace` for allmerged PRs. Historically this hasn't been all the feasible due to theamount of configuration required to control the number of warnings onCI, but with Cargo's new `[lint]` table it's possible to have aone-liner to silence all lints from Clippy by default. This commit bydefault sets the `all` lint in Clippy to `allow` to by-default disablewarnings from Clippy. The goal of this PR is to enable selective accessto Clippy lints for Wasmtime on CI.* Selectively enable `clippy::cast_sign_loss`This would have fixed #7558 so try to head off future issues with thatby warning against this situation in a few crates. This lint is stillquite noisy though for Cranelift for example so it's not worthwhile atthis time to enable it for the whole workspace.* Fix CI errorprtest:full List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

cc3bf3c0 - wasi-http: Allow embedder to manage outgoing connections (#7288)

Wed, 18 Oct 2023 23:02:59 +0000

wasi-http: Allow embedder to manage outgoing connections (#7288)This adds a new `send_request` method to `WasiHttpView`, allowing embedders tooverride the default implementation with their own if the desire. The defaultimplementation behaves exactly as before.I've also added a few new `wasi-http` tests: one to test the above, and twoothers to test streaming and concurrency. These tests are ports of the`test_wasi_http_echo` and `test_wasi_http_hash_all` tests in the[Spin](https://github.com/fermyon/spin) integration test suite. The componentthey instantiate is likewise ported from the Spin`wasi-http-rust-streaming-outgoing-body` component.Fixes #7259Signed-off-by: Joel Dice List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

f4be3606 - Refactor the test-programs test suite (#7182)

Mon, 09 Oct 2023 19:22:42 +0000

Refactor the test-programs test suite (#7182)* Refactor the test-programs test suiteThis commit is a large refactoring that reorganizes `test-programs` andhow we tests wasms in Wasmtime. Often writing tests requires complicatedinteractions with the guest which can't be done via hand-written `*.wat`syntax and requires a compiler to get engaged. For this purpose Wasmtimecurrently has the `crates/test-programs/*` test suite which builds filesfrom source and then runs the tests. This has been somewhat cumbersomein the past though and it's not been easy to extend this over time, sothis 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 ofthe tests, but this should not lose any tests (except one that wasn'tactually testing anything). Additionally the hope is that it's mucheasier 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 apreview2 executable is `preview2_*` and a CLI tests is `cli_*`. Whenbuilding the test suite an error is generated in the appropriate modulethen of "please write a test here", and then a test is written in thesame manner as the other tests in the module.* Remove no-longer-needed fetchesprtest: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 miriNeed to avoid wrappers for these cross-compiled targets* Break circular dependency for packagingDon't use the workspace dep for `wasmtime-wasi` since it injects aversion, instead use a `path = '..'` dependency to fool Cargo intodropping 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 modeThis commit is an attempt to fix some networking tests in synchronousmode in our test suite. Currently networking tests don't actually run insynchronous 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 insynchronous mode for me locally, most of the time. This appears to be aninteraction between how Tokio handles readiness and how we'reentering the event loop. We're effectively entering the Tokio event loopwith a future that's always ready which ends up starving Tokio ofotherwise performing its background work such as updating flags forreadiness of reading/writing.The fix here is to add a yield at the start of an `in_tokio` block whichis used in synchronous mode. This is a kludge fix but the intention isto enable Tokio to have a chance to update readiness flags and processevents from epoll/kqueue/etc.An additional fix to this issue is WebAssembly/wasi-sockets#64 where thetest is waiting on `READABLE` or `WRITABLE`, but in this specific caseit should only wait on `READABLE`. If it waited on just this then thatwould also fix this issue. Nevertheless having a `yield_now` is expectedto have little-to-no overhead and otherwise fix this edge case of analways-ready future.* Fix passing empty arguments on the CLI* Add another blocking accept* Update crates/test-programs/src/bin/api_proxy.rsCo-authored-by: Trevor Elliott ---------Co-authored-by: Trevor Elliott List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

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

Fri, 29 Sep 2023 14:41:38 +0000

Remove usage of `is-terminal` and `atty` crates (#7104)* Remove usage of `is-terminal` and `atty` cratesThis functionality is now folded into the standard library itself.* Fix syntax* Fix a unix/windows cfg List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

8a88ff6e - Wasi-http: support inbound requests (proxy world) (#7091)

Thu, 28 Sep 2023 22:51:51 +0000

Wasi-http: support inbound requests (proxy world) (#7091)* Move the incoming_handler impl into http_impl* Remove the incoming handler -- we need to use it as a guest export* Start adding a test-programs test for the server side of wasi-http* Progress towards running a server test* Implement incoming-request-method* Validate outparam value* Initial incoming handler test* Implement more of the incoming api* Finish the incoming api implementations* Initial cut at `wasmtime serve`* fix warning* wasmtime-cli: invoke ServeCommand, and add enough stuff to the linker to run trivial test* fix warnings* fix warnings* argument parsing: allow --addr to specify sockaddr* rustfmt* sync wit definitions between wasmtime-wasi and wasmtime-wasi-http* cargo vet: add an import config and wildcard audit for wasmtime-wmemcheck* cargo vet: audit signal-hook-registry* Remove duplicate add_to_linker calls for preview2 interfacesprtest:full* Add a method to finish outgoing responsesCo-authored-by: Adam Foltzer Co-authored-by: Pat Hickey * Mark the result of the incoming_{request,response}_consume methods as own* Explicit versions for http-body and http-body-util* Explicit `serve` feature for the `wasmtime serve` command* Move the spawn outside of the future returned by `ProxyHandler::call`* Review feedback---------Co-authored-by: Trevor Elliott Co-authored-by: Adam Foltzer List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml

a0469b11 - WASI preview 2 output-streams: new backpressure and flushing design (#6877)

Tue, 12 Sep 2023 17:26:31 +0000

WASI preview 2 output-streams: new backpressure and flushing design (#6877)* Stream backpressure v2Co-authored-by: Pat Hickey Co-authored-by: Trevor Elliott Co-authored-by: Dan Gohman Stop testing pseudocodeRestructure when notifications are sent, and make sure to flush the writerFix the wasi-http module versions of flush and blocking_flushUse blocking_write_and_flush for blocking writes in the adaptersFix a warning in wasi-httpRemove an unused DropPollableadd comment explaining try_write for tcpstreamrefactor: separate struct for representing TcpReadStreamby factoring into HostTcpSocket a little bittcp read stream: handle stream closingtcp tests: use blocking_read where its expecting to wait for inputmove common test body into wasi-sockets-tests/src/lib.rsensure parent socket outlives pollableinput and output streams can be children nowtcp's streams are the sockets childrentcp.wit: document child relationshipstcp tests: fix to drop socket after its child streamsreview feedback: propogate worker task panicstyleerror source fixtcp: use preview2::spawn, and propogate worker panicsjoin handle await always propogates panicbackground task handles ewouldblock as welldocument choice of constant* sync wit notes into wasi-http* improve wit docs for output-stream* doc: document `HostOutputStream` (#6980)* doc: document `HostOutputStream` Signed-off-by: Roman Volosatovs Co-authored-by: Pat Hickey * fix(wasi): fail when `MemoryOutputStream` buffer is full Signed-off-by: Roman Volosatovs --------- Signed-off-by: Roman Volosatovs Co-authored-by: Pat Hickey * rustfmtprtest:full* windows and doc fixes* cli test wasi-http: use blocking-write-and-flush* Disable some tests, and adjust timeouts when running under qemu* Try to reproduce the riscv64 failures* Update riscv to LLVM 17 with beta rust* Revert "Try to reproduce the riscv64 failures"This reverts commit 8ac678171ff3524fd1a6b8b4570c7fc2d42d3d1b.* Pin the beta version for riscv64* Fix a warning on nightly---------Signed-off-by: Roman Volosatovs Co-authored-by: Roman Volosatovs Co-authored-by: Trevor Elliott Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/test-programs/Cargo.toml