Joel Dice

Indeed, setting the memory pages limit to 1600 (i.e. 100MiB) allows the app the run without trapping.

What's left to do here? Do we need to make a 22.1 release that includes the x64 build of `clang` etc. instead of the x86 build?

Yeah, I'll put it on my to-do list and open a PR today or tomorrow.

This requires a Spin change. Currently, we use the default outgoing request handler provided by `wasmtime-wasi-http` (https://github.com/fermyon/spin/blob/b86af6c7188e84f5824f7eef757c65ff2ad265c4/crates/core/src/lib.rs#L236), which creates a new TCP connection and sends the request using `hyper`: https://github.com/bytecodealliance/wasmtime/blob/de0a9d7ce959d83a336d4f13487cf00e69e9efb2/crates/wasi-http/src/types.rs#L114....

@dlozina We'll need to create an outgoing http implementation from scratch based on `reqwest` instead of using the one provided by `wasmtime-wasi-http`, which is based on `hyper`. It shouldn't be...

@dlozina If you want to try making a PR for this, the code should go here: https://github.com/fermyon/spin/blob/b86af6c7188e84f5824f7eef757c65ff2ad265c4/crates/trigger-http/src/lib.rs#L694. You'll want to replace the `wasmtime_wasi_http::types::default_send_request(data, request)` line with code that translates the...

Hi all. Sorry about the somewhat scattered state of things at the moment. WASI 0.2.0 was just released a few weeks ago, and we're working on a [brand new Spin...

> Either way, @dicej would it make sense in the meantime to have Python 3.10, 3.11 and 3.12 supported on the `wasi-wheels` repo? (we have a hard requirement on 3.11...

Option 3 sounds good to me, too, but see also https://github.com/WebAssembly/wasi-libc/pull/429#discussion_r1295544604 for the discussion regarding `--no-gc-sections`. @yamt may have opinions about this.

FYI, I'm starting work on a subset of resource support in `wasm-compose`, specifically composing two components which import the same resource type such that they can pass handles to that...