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

Concurrent state does not operate as expected #18

Closed
bkvaluemeal opened this issue Aug 12, 2016 · 1 comment
Closed

Concurrent state does not operate as expected #18

bkvaluemeal opened this issue Aug 12, 2016 · 1 comment
Assignees
Labels
bug

Comments

@bkvaluemeal
Copy link

@bkvaluemeal bkvaluemeal commented Aug 12, 2016

During testing I have noticed that the concurrent state only calls the on_start() and on_stop() functions of the state that receives the arrow. In addition, when running a looping behavior like the one described in the image, only the on_enter() and on_exit() functions are called of the state that receives the initial state arrow inside the concurrent state.

I would expect all of the on_enter() and on_exit() functions for each internal state to get called every time the concurrent state is activated.

It works perfect the first time the concurrent state is activated, but then doesn't any other time the state is activated after the first. Killing the behavior and restarting it fixes the problem. I don't have to restart FlexBE for that to happen.

concurrent_test

Concurrent test behavior:
concurrent_test_behaviors.tar.gz

Log output when running the behavior:
concurrent_test.txt

The logger I used to test:
verbose_logger.txt
(It's a .py in disguise. GitHub wouldn't let me upload a .py)

@pschillinger

This comment has been minimized.

Copy link
Member

@pschillinger pschillinger commented Aug 14, 2016

Thanks for reporting and the helpful files! Yes, the events didn't get triggered correctly. I fixed it and tested your behavior, looks correct now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.