itowlson
itowlson
Thanks for catching this! `spin-kitchensink` is, I'm afraid, rather out of date - it dates from before Spin 0.1, and the SDK is now at 0.6 rather than the super-preview...
@adamreese bumping - sorry to nag but I don't think we have anyone else qualified to review this
Thanks for this. Might be worth checking out how the SpIn environment (https://github.com/fermyon/spin/tree/main/crates/http/src) sets up WAGI, because Spin also does extensive pre-warming that I think might go even further than...
Do you envisage asyncifying the call into the module, so that we can be returning the first bytes of the response as soon as the Wasm code produces them? Or...
Why did I think we would need to asyncify the call into the module? Well, we can't map stdout into a pipe that feeds directly into the response stream, because...
I started looking at this because it seems like it would be really useful - the service mesh example had been on my mind too. One difficulty I immediately ran...
The `arch` label from our point of view is at the Node level, not the Pod level - the virtual node implemented by the kubelet currently advertises an architecture. I'm...
@bacongobbler I think the composite provider-of-providers might be tricky with our current design. Adding a heterogeneous pod to the composite provider would require it to dispatch _individual containers_ to the...
Sorry for the lack of reply - I've been away. Thanks for this - I'll take a look!
Is this something we want to do? If so, I can take it.