Changes in instance_network.rs

d73bd632 - Migrate `wasmtime-wasi` to `wasmtime::error` (#12294)

Fri, 09 Jan 2026 17:28:46 +0000

Migrate `wasmtime-wasi` to `wasmtime::error` (#12294)* Migrate wiggle and wiggle generate to `wasmtime::error`* Fix testing `wiggle` and `wiggle-test` in isolationWhen doing plain old `cargo test -p wiggle` (or `wiggle-test`) the test wouldfail due to linking errors because Wasmtime's `std` cargo feature (and maybeothers) wasn't being enabled. The crate's tests would pass when run as part ofthe whole workspace, however, because of cargo feature resolution and othercrates that enabled the necessary features, which is why CI is green.* Remove direct anyhow dependency in wiggle-test* Migrate wasi-nn to `wasmtime::error`* Migrate wasi-keyvalue to `wasmtime::error`* Migrate wasi-io to `wasmtime::error`* Migrate wasi-http to `wasmtime::error`* Migrate wasi-config to `wasmtime::error`* Migrate wasi-common to `wastime::error`This is another interesting one because wasi-common is used internally toWasmtime but also by other projects. Therefore, rather than using`wastime::error::*` and making `wasmtime` a hard dependency, we use just`wasmtime_environ::error`.* cargo fmt* Migrate wasmtime-wasi to `wasmtime::error` List of files: /wasmtime-44.0.1/crates/wasi/src/p2/host/instance_network.rs

d5262995 - Mirror WASIp{2,3} sockets implementations (#11379)

Tue, 05 Aug 2025 17:09:58 +0000

Mirror WASIp{2,3} sockets implementations (#11379)This is an implementation of #11362 but for the `wasi:sockets`implementation of WASIp2. This additionally internalizes much of theWASIp3 implementation with `pub(crate)` to avoid unnecessarily exposingimplementation details of the crate. List of files: /wasmtime-44.0.1/crates/wasi/src/p2/host/instance_network.rs

f7a5aa34 - Unify WASIp{2,3} context structures (#11370)

Sat, 02 Aug 2025 00:57:09 +0000

Unify WASIp{2,3} context structures (#11370)This removes `wasmtime_wasi::p{2,3}::{WasiCtx, WasiCtxBuilder,WasiView}` in favor of only having `wasmtime_wasi::{WasiCtx,WasiCtxBuilder, WasiView}` instead. Conceptually these revisions of WASIall provide the same functionality just with a different veneer that thecomponent model offers, so having only one way to configure host-sidebehavior will make it easier to both organize implementations internally(e.g. more sharing of code) as well as for embedders to configure (onlyone context to create/manage). List of files: /wasmtime-44.0.1/crates/wasi/src/p2/host/instance_network.rs

0a074afc - Simplify WASI internal implementations (#11365)

Fri, 01 Aug 2025 01:24:24 +0000

Simplify WASI internal implementations (#11365)* Simplify WASI internal implementationsThis commit migrates the WASIp2 implementation to be closer to theupcoming WASIp3 implementation in terms of how things are implementedinternally. Previously the way things worked with WASIp2 is:* Embedders call `add_to_linker` with `T: WasiView`* Internally `add_to_linker` is called which creates `WasiImpl<&mut T>`* All internal implementations were `impl Host for WasiImpl where T: WasiView`* A forwarding impl of `impl WasiView for &mut T` was requiredWhile this all worked it's a bit complicated for a few reasons:1. Dealing with generically named structures like `WasiImpl` (or `IoImpl` or `WasiHttpImpl`) is a bit baroque and not always obvious as to what's going on.2. The extra layer of generics in `impl Host for WasiImpl` adds a layer of conceptual indirection which is non-obvious.3. Other WASI proposal implementations do not use this strategy and instead use "view" types or `impl Host for TheType` for example.4. Internal incantations of `add_to_linker` had to deal with mixtures of `IoImpl` and `WasiImpl` and aligning everything just right.5. An extra layer of generics on all impls meant that everything was generic meaning that `wasmtime-wasi`-the-crate didn't generate much code, causing longer codegen times for consumers.The goal of this commit is to migrate towards the style of what WASIp3is prototyping for how impls are modeled. This is done to increase theamount of code that can be shared between WASIp2 and WASIp3. This has anumber of benefits such as being easier to understand and also beingmore modular where `wasi:clocks` implementations of traits don't requirefilesystem context to be present (as is the case today). This in theoryhelps a more mix-and-match paradigm of blending together various bitsand pieces of `wasmtime-wasi` implementations.Concretely the changes made here are:* `WasiView` no longer inherits from `IoView`, they're unrelated traits now.* `WasiView` now returns `WasiViewCtx<'a>` which has `ctx: &'a mut WasiCtx` and `table: &'a mut ResourceTable`. That means it basically does the same thing before but in a slightly different fashion.* Implementations of `Host` traits are now directly for `WasiCtxView<'_>` and don't involve any generics at all. These are hopefully easier to understand and also better from a codegen/compile-time perspective.* Embedders no longer need to implement `IoView` directly and instead fold that functionality into `WasiView`.* `WasiHttpView` no longer inherits from `IoView` and instead has a direct `fn table` method. Additionally `WasiHttpImpl` no longer embeds `IoImpl` inside of it.* Host traits for `wasi:io` are now implemented directly for `ResourceTable` instead of `IoImpl`.The immediate goal of this refactoring is to enable more sharing alongthe lines of #11362. This was not possible prior because WASIp3 requiresa simultaneous borrow on the table/ctx while the trait hierarchypreviously gave you one-or-the-other. With this new organization it willbe possible to get both at the same time meaning morestructure/contexts/etc can be shared between implementations.prtest:full* CI fixes* More CI fixes* More CI fixes List of files: /wasmtime-44.0.1/crates/wasi/src/p2/host/instance_network.rs

7074afb6 - feat(wasip3): implement `wasi:sockets` (#11291)

Tue, 29 Jul 2025 23:35:32 +0000

feat(wasip3): implement `wasi:sockets` (#11291)* chore(wasip3): update `wasi:sockets` WITpull in `wasi:sockets` fromhttps://github.com/WebAssembly/wasi-sockets/pull/126Signed-off-by: Roman Volosatovs * refactor: rearrange Ctx/ViewSigned-off-by: Roman Volosatovs * refactor: name modules after packagesSigned-off-by: Roman Volosatovs * refactor: move `Network` to `p2`Signed-off-by: Roman Volosatovs * feat(wasip3): implement `wasi:sockets`Signed-off-by: Roman Volosatovs * refactor: reuse socket utilitiesSigned-off-by: Roman Volosatovs * test(wasip3): allow name resolution to failSigned-off-by: Roman Volosatovs * fix: expect macos-only var to be unused on other OSesSigned-off-by: Roman Volosatovs * refactor: whole buffer is written for UDPSigned-off-by: Roman Volosatovs * undo non-blocking writeSigned-off-by: Roman Volosatovs * extract buf capacity const, refactor tcp receiveSigned-off-by: Roman Volosatovs * introduce container struct for TCP non-inherited optsSigned-off-by: Roman Volosatovs * handle `listen` receiver closeSigned-off-by: Roman Volosatovs * refactor: clean upSigned-off-by: Roman Volosatovs * adapt to API changesprtest:fullSigned-off-by: Roman Volosatovs * refactor: check for listen receiver close each iterationSigned-off-by: Roman Volosatovs * Try to make test less flaky* Cut down on `#[cfg]` required for wasi:sockets* Fix test for real this time---------Signed-off-by: Roman Volosatovs Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/wasi/src/p2/host/instance_network.rs

73992063 - refactor: move wasip2 implementation to `wasmtime_wasi::p2` (#10073)

Tue, 15 Apr 2025 18:34:39 +0000

refactor: move wasip2 implementation to `wasmtime_wasi::p2` (#10073)* refactor: move `wasmtime-wasi` p2-specific functionality to `p2`Signed-off-by: Roman Volosatovs * doc: move some of the p2 comments to top-levelSigned-off-by: Roman Volosatovs * chore: shorten `network` and `filesystem` module namesSigned-off-by: Roman Volosatovs ---------Signed-off-by: Roman Volosatovs List of files: /wasmtime-44.0.1/crates/wasi/src/p2/host/instance_network.rs