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

Get current behavior after executed first time #69

Open
kanehuang opened this issue Feb 25, 2019 · 2 comments
Open

Get current behavior after executed first time #69

kanehuang opened this issue Feb 25, 2019 · 2 comments

Comments

@kanehuang
Copy link

Hello,

I am using behaviors without operator and want to get correct executing behavior to know the current process. The process is launch roslaunch flexbe_onboard behavior_onboard.launch run flexbe_widget be_action_server and flexbe_mirror. It used to be an unstable process to get current behavior and somehow related to flexbe_mirror threading problem which has been fixed by adding threading lock. However, it also introduces another issue that we can get first and only the first behavior. It seems caused by return without releasing the lock. If I released the lock at the end of _mirror_callback function, things look good to me. I can get current behaviors after second time executing. Do you thing that is the cause/fix to this problem?

@kanehuang kanehuang changed the title Get current behavior after executed first behavior Get current behavior after executed first time Mar 4, 2019
@pschillinger
Copy link
Member

Thank you for reporting! I am not sure if I understand you correctly, though. Can you add the steps that I would need to execute to reproduce the problem?

If you think you already found a way to fix it, that's great! If you open a pull request, I can check your proposed change.

@dcconner
Copy link
Member

Any further discussion on this before I close?

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

3 participants