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

Re #48 manually handle signals in wobbler example #49

Closed
wants to merge 1 commit into from

Conversation

rethink-imcmahon
Copy link
Contributor

This commit removes reliance on rospy for handling the shutdown
behavior when a Ctrl+C signal is asserted on the joint_velocity_wobbler
example. Cleanup was not properly being executed in only the
simulated robot through rospy's on_shutdown() callback handler. This
change has been tested on both the simulated and real Baxter robots.

This commit removes reliance on rospy for handling the shutdown
behavior when a Ctrl+C signal is asserted on the joint_velocity_wobbler
example. Cleanup was not properly being executed in only the
simulated robot through rospy's on_shutdown() callback handler. This
change has been tested on both the simulated and real Baxter robots.
@rethink-imcmahon rethink-imcmahon force-pushed the rospy_simulated_wobbler_fix branch from 57a0e16 to b884675 Compare September 8, 2015 19:22
@rethink-imcmahon
Copy link
Contributor Author

Either this should get fixed in all 13 of our examples with on_shutdown behavior or the root cause needs to be sussed out in ros_comm/rospy in simulation

@rethink-imcmahon
Copy link
Contributor Author

Appears there was an underlying rospy issue in ros_comm:
ros/ros_comm@2e84880
ros/ros_comm#690

This PR is no longer needed :)

@rethink-imcmahon rethink-imcmahon deleted the rospy_simulated_wobbler_fix branch December 18, 2015 16:40
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

Successfully merging this pull request may close these issues.

2 participants