wasmtime / issue #14857 Named WASI contexts must share on... · git-wasmtime

Stream: git-wasmtime

Topic: wasmtime / issue #14857 Named WASI contexts must share on...

Wasmtime GitHub notifications bot (Oct 19 2026 at 20:46):

When using named imports with wasmtime-wasi (add_named_to_linker), the per-name contexts have to share the default ResourceTable, but nothing says so, and WasiHttpNamedView's docs suggest the opposite ("need not be unique").

Named implementations push resources into the named view's table, while the plain interfaces that consume them (e.g. wasi:io/streams in p2) read the default table. With a table per id, reading a labelled wasi:cli/stdin returned the default context's input in a test, and p3 http fails with failed to delete request from table.

At minimum this needs documenting on WasiNamedView/WasiHttpNamedView. An API that returns the per-id context and the shared table separately would make it impossible to get wrong.

Wasmtime GitHub notifications bot (Oct 19 2026 at 21:18):

alexcrichton added the wasm-proposal:component-model-implements label to Issue #14857.

Wasmtime GitHub notifications bot (Oct 20 2026 at 20:42):

alexcrichton closed issue #14857:

When using named imports with wasmtime-wasi (add_named_to_linker), the per-name contexts have to share the default ResourceTable, but nothing says so, and WasiHttpNamedView's docs suggest the opposite ("need not be unique").

Named implementations push resources into the named view's table, while the plain interfaces that consume them (e.g. wasi:io/streams in p2) read the default table. With a table per id, reading a labelled wasi:cli/stdin returned the default context's input in a test, and p3 http fails with failed to delete request from table.

At minimum this needs documenting on WasiNamedView/WasiHttpNamedView. An API that returns the per-id context and the shared table separately would make it impossible to get wrong.

Last updated: Oct 31 2026 at 23:03 UTC