Pat Hickey

A wasm runtime must use a 64k page size to be spec compliant: https://webassembly.github.io/spec/core/exec/runtime.html#syntax-meminst - its required for the data segment and the memory instructions to work correctly. Changing that...

Yes, this seems like the right thing to do to support multi-module namespacing. Go for it!

I'm up for exploring this idea more sometime in the future, but for the preview2 timeframe I have advocated that we keep interfaces and concepts that existed in preview 1...

This discussion is about the wasi-filesystem wit proposal, which is targeting being part of preview 2. Preview 1 is done and we aren't going to add or remove any parts...

One way out of this is to put the burden of resolving `.` and `..` in paths to userland, and not permitting either to be used in paths passed to...

Can you please run wasmtime with the environment variable `RUST_LOG=wasi_common=trace` to provide additional debug information? That will help us determine whether this is a wasmtime or libc issue.

Thanks. Can you please move this bug over to the wasmtime repository? This appears to be a bug over there, not in wasi-libc.

This is a bug in Wasmtime 9.0.{0,1}. I have prepared a fix which we will release as 9.0.2. The behavior is the same across wasi-sdk 19 and 20, I did...

This is a clang issue rather than a libc issue, I'm not an expert on clang but maybe @sbc100 can point you in the right direction?

Yes, we should follow the lead of `splice(2)` and not throw away read bytes if a write fails. I was lazy about doing that correctly in wasmtime's implementation, but the...