Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UsageModelPassedElement event sometimes delivered in wrong order. #81

Open
stiesssh opened this issue Jul 26, 2024 · 0 comments
Open

UsageModelPassedElement event sometimes delivered in wrong order. #81

stiesssh opened this issue Jul 26, 2024 · 0 comments

Comments

@stiesssh
Copy link
Collaborator

stiesssh commented 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 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.

@stiesssh stiesssh changed the title UsageModelPassedElemet event sometimes delivered in wrong order. UsageModelPassedElement event sometimes delivered in wrong order. Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant