On shutdown hooks about rclpy HOT 5 CLOSED

I wonder if this was just my immediate reaction to not having something that was there in ROS1. Looking at the situation with fresh eyes, I wonder if it really is the right thing to have the application take care of the shutdown. It is only the application that will know that foo.shutdown() might need to happen before bar.shutdown() lest something catastrophic happen and the world end.

In this case it would be each class's responsibility to agnostically provide an on_shutdown method.

from rclpy.

@stonier Based on your latest comment, I'm going to close this out for now. If you feel like this is something that core rclpy needs to provide in the future, please feel free to reopen.

from rclpy.

I'd be interested to know if there was an explicit reason it was made available in the ROS 1 api. We could perhaps trawl the rospy issues and commit history to see if there is anything there.

from rclpy.

Unfortunately, it looks like in ros_comm that code comes from this commit: ros/ros_comm@5ac90fafe3 ,which looks like it is probably the port from sourceforge -> github in 2010. To go further back than that, we'd have to go trawling through the original sourceforge stuff, which I don't think is worth it. Maybe @tfoote has some recollection on why it was originally added.

from rclpy.

On gazebo_ros_pkgs we have a use case where we want to make a service call right before shutdown. On ROS 1 the on_shutdown hook was being used:

https://github.com/ros-simulation/gazebo_ros_pkgs/blob/3cd100e20ba09245be01ad674248aa31a46ad271/gazebo_ros/scripts/spawn_model#L315-L317

If the hook isn't ported, is there an alternative way to achieve this?

That script is being migrated to ROS 2 on ros-simulation/gazebo_ros_pkgs#948

from rclpy.