Brooks Townsend
Brooks Townsend
This can be done in such a way that preserves git history, and we should do that by merging the two histories of `wascap` and wasmcloud.
Hey @Taction , @jordan-rash has been pioneering the Go SDK for writing capability providers in Go 😄 The [litestream provider](https://github.com/jordan-rash/litestream-provider) is an example of this, and he's currently touching up...
This also seems to still reproduce the same issue, likely because the image tag doesn't exist so it's unwrapping to `latest` as a fallback ``` > wash claims inspect echo_s.wasm...
> Do you have suggestions ? besides a more detailed message. So what we're really trying to do here is provide a useful error message for people when they try...
@tessi would love to help out here, especially if you're close! Would you be willing to publish that fork and give a quick TL;DR on what you've tried and what's...
Thank you for the great updates @tessi, I'm following along here but haven't had much free time to look into it yet
Perfect timing here, Wasmtime just announced 1.0! Very exciting 😄
Closing in favor of #501 as it better describes a good solution
@thomastaylor312 I know this is a possible race condition, but doesn't this work the other way? In the above case where you handle existing data and THEN handle events, couldn't...
Thank you @wamli ! > Interesting observation: wash pull wasmcloud.azurecr.io/httpserver:0.19.1 is totally relaxed and pulls it. This is the strangest part for me, which makes this issue a little different...