Tomoya Fujita

@jdlangs thank you very much for your contribution. I would suggest that you can create PR against rolling 1st, then we can backport them to Iron and Humble.

Note, original issue detected on Foxy, we need to backport all supported ROS 2 distribution (humble, galactic and foxy)

@suurjaak sorry i was not thinking clearly before, but i am with @clalancette on this. this behavior change might break the ROS 2 user space. I consider that would be...

IMO, i totally understand your point. this kind of policy should be simple as much as possible, once we have exception that will be hard to keep afterwards. So i...

@suurjaak thanks for the contribution, the issue has been also closed accordingly.

I agree with this approach. This would be worth to discuss in general for ROS 2 client libraries perspective, including `rclcpp`. - There are other classes that `exception_callback` should be...

CI: * Linux [](http://ci.ros2.org/job/ci_linux/17717/) * Linux-aarch64 [](http://ci.ros2.org/job/ci_linux-aarch64/12263/) * Windows [](http://ci.ros2.org/job/ci_windows/18342/)

@adityapande-1995 can you review this?

@Mergifyio backport to humble

CI: * Linux [](http://ci.ros2.org/job/ci_linux/16617/) * Linux-aarch64 [](http://ci.ros2.org/job/ci_linux-aarch64/11201/) * Windows [](http://ci.ros2.org/job/ci_windows/17010/)