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
In caseStop() we call this.switch(...) to reenter the loop.
As a result we kind of process the Stop and Start at the same time and we also end up with two UsageModelPassedElement events in the result set.
Problem
The order of deliverance of events from one result set is arbitrary. Thus, if a UsageModelPassedElement<Start> and aUsageModelPassedElement<Stop> are part of the same result set (as is the case here) the UsageModelPassedElementmight be delivered before theUsageModelPassedElement`.
In most cases, this should not matter at all. However, it breaks my MENTOR state exploration, and is also kinda problematic from a semantic perspective, i guess.
The text was updated successfully, but these errors were encountered:
stiesssh
changed the title
UsageModelPassedElemet event sometimes delivered in wrong order.UsageModelPassedElement event sometimes delivered in wrong order.
Jul 26, 2024
Context
I have any usage model with a loop.
In caseStop() we call
this.switch(...)
to reenter the loop.As a result we kind of process the
Stop
andStart
at the same time and we also end up with twoUsageModelPassedElement
events in the result set.Problem
The order of deliverance of events from one result set is arbitrary. Thus, if a
UsageModelPassedElement<Start>
and aUsageModelPassedElement<Stop>
are part of the same result set (as is the case here) the UsageModelPassedElementmight be delivered before the
UsageModelPassedElement`.In most cases, this should not matter at all. However, it breaks my MENTOR state exploration, and is also kinda problematic from a semantic perspective, i guess.
The text was updated successfully, but these errors were encountered: