Joel Dice

Does `wasmtime serve -O pooling-allocator=n -S cli ` work? As of recent versions of Wasmtime, the pooling allocator is used by default, and it has a memory limit of 10MB,...

https://github.com/bytecodealliance/wasmtime/pull/8849 should address this, although we'll probably need to wait until Wasmtime 23 for it to land in a release.

I believe this was addressed by https://github.com/bytecodealliance/wasmtime/pull/8849

Hi @JamesParrott. Yeah, the size is annoying, I agree. You can reduce it somewhat using e.g. `wasm-tools strip --all` (after installing https://github.com/bytecodealliance/wasm-tools/). Otherwise, I don't know of any great options...

> Re: the host, it's not the wheel or sdist size. When running `python3 -m wasmtime.bindgen app.wasm --out-dir hello_host`, the resulting hello_host contains a Python package, and 40 .wasm files....

I believe @brettcannon is planning to add `zlib` to the WASI build of CPython, along with other native modules such as `bzip2`, etc. Regarding `requests`: I agree that this would...

That sounds fine to me. The main thing I'm looking for is an easy way to say: "Fully sandbox this component, giving it access only to what I've explicitly granted."...

> @dicej with this version I'm seeing errors like > > ``` > ---- variants::run stdout ---- > Error: failed to read component type file: VariantsWorld_component_type.o > > Caused by:...

I don't have much experience with `wasm-bindgen`, and the error messages aren't telling me much. I just tried reproducing this locally after upgrading to Rust 1.82, but the tests all...

Yeah, that's a good example where, instead of `unwrap`ping, we should at least panic with an informative message and a Python-level backtrace, e.g. "expected string value, got value of type...