Guy Bedford
Guy Bedford
When the written body is less than the content length, the only error code that fits is `internal-error`. But when the written body is more than the content length, perhaps...
As far as I can tell, `outgoing-body`'s stream can exist in two different states: 1. unattached to the http request, before the request is made - all writes buffer, and...
In the current WIT definitions, `outgoing-body` `finish` defines that the content length must be validated against the actual length. But, in addition to this, the Wasmtime implementation also throws a...
The new WASI reactor definition is now: ``` default world reactor { import wall-clock: clocks.wall-clock import monotonic-clock: clocks.monotonic-clock ... } ``` That is, from a WIT perspective, the identifying import...
I wonder if it might be worth making the "context" argument for wasi logging entirely optional? This way, both global and contextual logging could be supported.
I've got a component which executes as a command via `main()`, after which exported functions may be called as part of an extended lifecycle for the application. I'm finding that...
Updates to [email protected].
@dicej did some exploration here on what would be involved in https://github.com/dicej/WASI-Virt/commit/99d950f104d60899865dd133ad3a2b113b4672ca. This currently hits limitations with wasm-compose due to a cyclical case, which would need to be acyclified via...
The filesystem created by WASI-Virt is currently read-only for what is mounted. We should add full dynamic filesystem support as well as a layer over the read-only mounts.
We should add support for symlink mounting in WASI-Virt.