itowlson

@calebschoepp Is this superseded by the OpenTelemetry work?

Tool setup is a long wished for improvement! Unfortunately, from the `spin doctor` work and earlier investigation of doing tool setup from templates, I recall it got kinda hard to...

Those look really nice, and much more nuanced than the aside format. Great find!

@divya-mohan0209 Do you know which version of the shim you have in the k3d cluster? It's a bit hard to tell from the containerd-wasm-shims quickstart. There's a Discord thread (https://discord.com/channels/926888690310053918/1122332926244294806/1124380791846219886)...

@divya-mohan0209 I've raised an issue for the different versions. It looks like the shim quickstart was updated within the last hour to new versions; the previous one looks quite old...

@devigned I think you have some clippies (and autoformats maybe?) that are unrelated to the changes. I believe these are already picked up in #2569 so you'll probably need to...

@devigned What's the status of this? I believe we're keen for it if you still have bandwidth - is it just the review nits and the lints?

@devigned You'll need to run `make update-cargo-locks` to get CI to pass. (This happens because new/changed dependencies in the trigger crate need to feed through into the lockfile for the...

Integration test failure seems unrelated (it's hitting one of my PRs too).

Spin talks to guests (Wasm applications) using the [WebAssembly component model](https://component-model.bytecodealliance.org/). You can find the interface declarations at https://github.com/fermyon/spin/tree/main/wit - in particular we track the `wasi-http` specification for HTTP applications....