You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some very quick testing via cargo-wasi shows that everything except colored output appears to work (probably need to add some support for something in termcolor). From a release build wasmtime appears to need ~7s on a Macbook Air to JIT the optimized wasm blob on first run, and it's pretty much instantaneous on future runs.
How to actually do this? 🤷♂
One additional thing I would like to do with this is to sandbox the tool more. The only thing it needs access to is stdin+stdout+args, all network and filesystem access should be disabled. It doesn't look like running from wasmtime as a CLI tool supports this, so maybe cbor-diag-cli should use wasmtime as a library if there's some way to do so there.
The text was updated successfully, but these errors were encountered:
Some very quick testing via
cargo-wasi
shows that everything except colored output appears to work (probably need to add some support for something intermcolor
). From a release buildwasmtime
appears to need ~7s on a Macbook Air to JIT the optimized wasm blob on first run, and it's pretty much instantaneous on future runs.How to actually do this? 🤷♂
One additional thing I would like to do with this is to sandbox the tool more. The only thing it needs access to is stdin+stdout+args, all network and filesystem access should be disabled. It doesn't look like running from
wasmtime
as a CLI tool supports this, so maybecbor-diag-cli
should usewasmtime
as a library if there's some way to do so there.The text was updated successfully, but these errors were encountered: