Bug: Parallel states transitions behave differently on V5

[gastonfartek]

Bug: Parallel states transitions behave differently on V5

[Andarist]

This works as expected according to the SCXML semantics of conflicting transitions (see removeConflictingTransitions.

However, we have tweaked rules around reentrancy of source states (see here). Essentially, for many purposes we are using LCA over LCCA algorithms to detect "transitions containment". This makes this part of the mentioned removeConflictingTransitions algorithm outdated for us:

Transitions that aren't contained within a single child force the state machine to leave the ancestor (even if they reenter it later).

Our own implementation is still using our own computeExitSet though so it could work correctly already - maybe there is a small bug there. I'm still trying to think through this case but it feels like - given the above - you are right that this should work.

Note though that:

• respective source regions are still exited here (and reentered). It's just that the parallel region itself isn't reentered here whereas in SCXML it would be
• using on in a final state is forbidden by SCXML but it turns out that we don't quite enforce this

[davidkpiano]

We're going to look into this a bit more... may be a bug.