Stream: wasi

Topic: ✔ Is the wasip3 http implementation incomplete?

Roman Volosatovs (Jun 05 2025 at 15:06):

We do actually have tests for wasip3 outgoing HTTP, so I'd expect it to work, here's how we set them up https://github.com/bytecodealliance/wasip3-prototyping/blob/a759b5c37fdd3a7b5110a33fa24b624c2baee5d4/crates/wasi-http/tests/all/p3/outgoing.rs#L28-L35

could you share the code you use to configure WASI?

Alex Crichton (Jun 05 2025 at 15:33):

You might be running into a mismatch where Wasmtime is using a fork of the WIT files with the async keyword which we haven't yet upstreamed to the wasi-http repository (that's on me)

Alex Crichton (Jun 05 2025 at 15:33):

so this might be a WIT-sync-ing problem

mainrs (Jun 05 2025 at 15:42):

Alex Crichton said:

You might be running into a mismatch where Wasmtime is using a fork of the WIT files with the async keyword which we haven't yet upstreamed to the wasi-http repository (that's on me)

I did not notice the additional async keyword, thank you! I think that was the issue that caused the error message. It now instantiates and links properly after adding the keyword locally.

I'm hitting other issues now: as soon as my WASI function contains an await, the VM panics with an unreachable. Time to dig into wasmtime source code again :D

Notification Bot (Jun 05 2025 at 15:42):

mainrs has marked this topic as resolved.

Last updated: Dec 06 2025 at 06:05 UTC