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
Currently we always initialise new components to some "initial state" when we spin them up. It would be nice to be able to "load" the end state from a previous test run in order to be able to pick up and continue testing from where we left off. It would also be nice to be able to "patch" the state of a running component to do hotfixes or simulate byzantine faults.
Note that something special would have to be done with the Init() messages if a test is resumed.
The text was updated successfully, but these errors were encountered:
Currently we always initialise new components to some "initial state" when we spin them up. It would be nice to be able to "load" the end state from a previous test run in order to be able to pick up and continue testing from where we left off. It would also be nice to be able to "patch" the state of a running component to do hotfixes or simulate byzantine faults.
Note that something special would have to be done with the
Init()
messages if a test is resumed.The text was updated successfully, but these errors were encountered: