You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue simply serves as a list of things that we've found while writing wadm 0.4 that we wish would change in the OTP host, ranging from adding an additional field on an event to changing structure of commands, etc.
Most of this is just a stream so they shouldn't be taken as must-do's, but after the release of wadm 0.4 we'll consider this list and what we can do to improve the efficiency of wadm and the host
Would be really nice to implement instantiate-on-request actors, effectively removing the need to deal with actor counts and scale. "starting" an actor on a host could have an optional "max" count, but otherwise it just instantiates when it receives a request and exits. The below checkmarks assume that the checkmark above is not implemented for a while
Would be nice for the host heartbeat to contain enough information to uniquely identify actors that belong to spreads, e.g. a combination of annotations to counts or vice versa
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!
This issue simply serves as a list of things that we've found while writing wadm 0.4 that we wish would change in the OTP host, ranging from adding an additional field on an event to changing structure of commands, etc.
Most of this is just a stream so they shouldn't be taken as must-do's, but after the release of wadm 0.4 we'll consider this list and what we can do to improve the efficiency of wadm and the host
The below checkmarks assume that the checkmark above is not implemented for a while
The text was updated successfully, but these errors were encountered: