Brooks Townsend
Brooks Townsend
No not at all! I appreciate the reminder, and I'm glad the fix showed up as something that would resolve this 😄 Thank you @brettjrea
``` ~$ wash up --nats-connect-only --wasmcloud-version v1.0.2 🏃 Running in interactive mode. 🎛️ To start the dashboard, run `wash ui` 🚪 Press `CTRL+c` at any time to exit 2024-05-08T14:11:49.437567Z INFO...
When we solve this issue, I definitely want to clarify here exactly the blast radius that we can reproduce. A hanging shutdown is more acceptable (IMO) than a component affecting...
This is primarily resolved by #2000 and #2017
Closing because of ☝🏻
Hey @brianw-0, I think this is a simple rename error from migrating the blobby wadm manifest 😞 The problem lies on this line: https://github.com/wasmCloud/wasmCloud/blob/main/examples/rust/components/blobby/wadm.yaml#L24 The `linkdef` trait is considered a...
I didn't consider that merging the PR would mark this as "completed", I was able to make it work with this fix but please let me know if it works...
Woah, that's surprising. That error is coming back from the standard Rust library, so it must be an issue we need to compensate for in our blobstore provider. I suppose...
Alrighty @brianw-0 , if you wouldn't mind trying with `ghcr.io/wasmcloud/blobstore-fs:0.6.1` that should fix the creation time issue 😄 One more bug squashed
@brianw-0 just checking in here, did this help with the problem? Just want to make sure that the blobstore call went all the way through 🙂