The recent fix to #54 introduced a new bug whereby it is possible for a transition to get stuck in the STARTED state (for example if one of its tweets throws an error upon initialization), and it can never leave this state because a subsequent transition will not interrupt transitions in this state. (In fact it might even cause an infinite loop as the interrupting transition repeatedly defers itself?)
We will probably need to check whether a transition is stuck and to allow the transition to proceed.
mbostock
commented
8 years ago
The recent fix to #54 introduced a new bug whereby it is possible for a transition to get stuck in the STARTED state (for example if one of its tweets throws an error upon initialization), and it can never leave this state because a subsequent transition will not interrupt transitions in this state. (In fact it might even cause an infinite loop as the interrupting transition repeatedly defers itself?)
We will probably need to check whether a transition is stuck and to allow the transition to proceed.