Brooks Townsend
Brooks Townsend
**Describe the bug** I was attempting to inspect an actor file when I had the incorrect filename, and I got the following error: ``` wash claims inspect build/echotg_s.wasm Pulling artifacts...
With `cross`, we should be able to release builds for linux and mac arm64 architectures similar to how we do it with https://github.com/wasmCloud/capability-providers
`wash` has grown significantly in scope over the last few years, and we have a decent list of packages in our `Cargo.toml` that warrants a sweep and audit to see...
**Is your feature request related to a problem? Please describe.** When building and signing actors, `wash` certainly improves over previous processes by autogenerating keys for actor and provider modules. However,...
**Is your feature request related to a problem? Please describe.** wash contexts are designed to make working with different wasmCloud clusters easy by allowing you to easily swap from one...
**Is your feature request related to a problem? Please describe.** `wash drain` currently has 4 options, `all`, `lib`, `oci`, `smithy`. These are useful for managing the cache collected by wasmCloud,...
It would be valuable for `wash` to support some form of parJEEzy verification method, perhaps `wash par check` or `wash par verify`. This verification process would involve inspecting the par...
`wascap` is primarily used by wasmCloud, and in the interest of consolidating our crates and repositories it should be relocated to the `crates/` subdirectory of the [wasmCloud](https://github.com/wasmCloud/wasmCloud) repo.
In #467 I added the `provider_start_failed` event to this scenario, but really we should return a failed ack in this case.
**Describe the bug** When you stop a wasmCloud host, it publishes two `host_stopped` events in the process of shutting down. With the [lattice-observer](https://github.com/wasmCloud/lattice-observer), this can end up double-handling the same...