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
When manifest changes, depending on the timing it is possible for newly
generated valid leases to get removed if the sign message loop attempts
to sign messages that are as a result of progressing previous network.
Here is an example scenario in a specific order that was causing itests
to fail:
* participants get a lease for network A up to instance 5
* network A progresses to instance 6
* manifest changes the network name to B
* participants get a new lease for network B up to instance 5
* sign loop receives a message from network A, instance 6
* `getParticipantsByInstance` lazily removes leases since it only
checks the instance.
* the node ends up with no participants, and stuck.
To fix this:
1) check if participants asked for are within the current network, and
if not refuse to participate.
2) check network name, as well as instance, to lazily remove expired
leases.
0 commit comments