Fix segfault by adding __enter__ and __exit__ to Waitable (backport #761)#998
Fix segfault by adding __enter__ and __exit__ to Waitable (backport #761)#998
Conversation
Also make QoS event waitable use it. This fixes a crash when another thread is spinning on a destroyed subscription using cyclonedds. Signed-off-by: Shane Loretz <sloretz@openrobotics.org> (cherry picked from commit a75529d)
Signed-off-by: Tully Foote <tfoote@osrfoundation.org>
|
This is causing users unexplained segfaults in foxy. This patch has been verified to solve the solution for them. |
|
@ros-pull-request-builder restest this please |
|
@ros-pull-request-builder retest this please |
|
Looks like the tests are flakey: https://build.ros2.org/job/Fpr__rclpy__ubuntu_focal_amd64/77/ failed but https://build.ros2.org/job/Fpr__rclpy__ubuntu_focal_amd64/78 passed on the same commit. Test Result (5 failures / +5)projectroot.test_action_serverprojectroot.test_timerrclpy.rclpy.test.test_action_server.TestActionServer.test_different_feedback_type_raisesrclpy.rclpy.test.test_timer.test_number_callbacks[0.001]rclpy.rclpy.test.test_timer.test_cancel_reset[0.001]Test Result (5 failures / +5) |
|
The windows failure looks independent and likely executor related. |
|
The Windows failures are unrelated. Here's a baseline for Windows I ran not too long ago: https://ci.ros2.org/job/ci_windows/17425/ |
sloretz
left a comment
There was a problem hiding this comment.
Looks backportable to me.
This is an automatic backport of pull request #761 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com