Brooks Townsend
Brooks Townsend
**Describe the spike** More information is needed, but in the case where an actor panics and dies we should be able to terminate the genserver with a helpful error message,...
**Describe the bug** When a capability provider starts there is a period of time between the start of initialization and the time where the provider sets up its nats subscriptions....
**Is your feature request related to a problem? Please describe.** After doing some testing with IoT devices, it's fairly easy to exceed available memory and have the process killed. With...
**Is your feature request related to a problem? Please describe.** As a part of terminating a provider we send a shutdown message, and after a specified timeout we run `kill...
**Describe the bug** This bug only applies when the capability provider NATS connection is separate from the lattice NATS connection. As you can see in the `perform_rpc_invoke` function here https://github.com/wasmCloud/wasmcloud-otp/blob/main/host_core/lib/host_core/web_assembly/imports.ex#L390-L398,...
**Describe the bug** This can probably also happen with actors but with provider's it's more noticeable due to the OCI artifact size. When you issue a request to the control...
Below is an incomplete list of operations we can use in the dashboard - [x] Delete link defininitions https://github.com/wasmCloud/control-interface/issues/3 - [ ] Query oci references (tab with a display table)...
The Github action we currently use to build `host_core` allows failures with the Credo step and the Dialyzer step, in order to let us cache results and continue with our...
Currently, when a host is stopped all actors are also stopped, but capability providers may remain running. These orphaned providers may take up system resources like CPU/memory and they may...
Similar to `wash drain`, the dashboard should have a trashcan icon on the local host that can clear the wasmCloud cache on the local machine.