Brooks Townsend
Brooks Townsend
This is probably better as a wadm manifest https://github.com/wasmCloud/wadm/tree/main/oam, and I think that support for this would likely overlap significantly with the goals of wadm
No longer applicable as actor health isn't shown in the dashboard (due to how unreliable it is as a metric)
Marking this as `good first issue` as this is a great place to contribute small but very impactful fixes to the host runtime. There are many places where we are...
Just commenting after our discussion; that is correct, we also have a provider RPC connection which is separate from the lattice RPC connection. When these two connections are separate we...
cc @autodidaddict as we ran into this during our debugging session today (not asking for you to fix it, just making you aware)
This issue is encompassed by #376 so I'm closing this in favor of it. It's still valuable information but not worth keeping two issues open for the same problem
It appears that an actor that panics or crashes will show as "unhealthy" but the ActorModule will not be removed
furthermore, this `Unhealthy` will just get swallowed if you start another instance of the actor
Desired goal: If an actor panics during execution, the GenServer `ActorModule` should restart
This can now be done with an update to wasmex https://github.com/tessi/wasmex/releases/tag/v0.7.1