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

update_configuration needs timeout #100

Open
lucasw opened this issue Feb 26, 2018 · 1 comment
Open

update_configuration needs timeout #100

lucasw opened this issue Feb 26, 2018 · 1 comment

Comments

@lucasw
Copy link

lucasw commented Feb 26, 2018

If a dynamic reconfigure server locks up update_configuration never returns.

My client ( https://github.com/lucasw/dynamic_reconfigure_tools/blob/master/rqt_dr_single ) runs update_configuration out of a rospy Timer update callback, this locks up the whole rqt window and turns it gray when the dynamic reconfigure server locks up (does that mean Timer is running in the Qt thread and if so why?).

rqt_reconfigure doesn't have the same locking up problem but it is creating a thread to run update_configuration within- I can copy that but maybe solving the timeout here would be better.

I'll make https://github.com/lucasw/dynamic_reconfigure_tools/blob/master/rqt_dr_single/scripts/example_server.py demonstrate the problem (e.g. first reconfigure callback works, second waits forever) and post the code here.

lucasw added a commit to lucasw/dynamic_reconfigure that referenced this issue Feb 28, 2018
lucasw added a commit to lucasw/dynamic_reconfigure_tools that referenced this issue Sep 27, 2018
…ception doesn't go to the right place- instead create a thread for every update_configuration (what happens to the stuck ones though?) #15 ros/dynamic_reconfigure#100
@130s
Copy link
Member

130s commented Jul 23, 2021

My client (...) runs update_configuration out of a rospy Timer update callback, this locks up the whole rqt window and turns it gray when the dynamic reconfigure server locks up

I'm also seeing a rospy client hanging up as well. My client isn't running in Timer callback either. In rqt_reconfigure I don't find it called from Timer's callback either though (it's a shame as an original author almost 10 years ago what was my thought in doing that).

@lucasw Do you remember how you ended up solving/working this around?

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

2 participants