Currently it's possible for there to be a transition assertion hanging in the arbiter after a failed state move. This hanging assertion is not cleared when the error is reset.
It's unclear exactly why this happens, but we expect that the transition assertion should no longer apply after a failed move if we didn't even get started, and should continue to apply if we got started and had to stop in the middle.
Currently it's possible for there to be a transition assertion hanging in the arbiter after a failed state move. This hanging assertion is not cleared when the error is reset.
It's unclear exactly why this happens, but we expect that the transition assertion should no longer apply after a failed move if we didn't even get started, and should continue to apply if we got started and had to stop in the middle.