-
Notifications
You must be signed in to change notification settings - Fork 172
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
Use try_shutdown() instead of shutdown() in DirectNode.__exit__() #683
Conversation
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me with green CI. Thanks @ivanpauno
The Rpr checker results don't look great .... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fixes the error for me, too. Looks good with green CI.
CI again after ros2/rclpy#868 got merged: |
Just as an FYI, I retested the original problem with ros2/rclpy#868 and this applied, and it seems to succeed for me here. So 👍 from me, thanks! |
I have made a new rclpy release, I will rerun the Rpr checker in a few hours, it should pass this time. |
@ros-pull-request-builder retest this please |
Looks like it is still rebuilding: https://build.ros2.org/view/Queue/ |
@ros-pull-request-builder retest this please |
Thanks for the fix, @ivanpauno! I'm going to merge this in so that I can run CI for switching the default DDS: ros2/rmw#315 |
There was a change in signal handling, and now SIGINT/SIGTERM will automatically trigger a shutwon request.
This modifies
DirectNode.__exit__()
to usetry_shutdown()
, in order to not get a "context already shutdown" error when a signal is sent.I manually tested with the following example and the issue is gone:
New error message after ctrl-c: