You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WIP. Need some help isolating why this might be happening so I can create reproducible example. This issue is to get the conversation started, and see if others have seen something similar in the wild.
Expected behavior
No exception
Actual behavior
Occasional failures. Here are 2 examples of Tracebacks we've had happen on our robots, in the wild:
Example 1
Traceback (most recent call last):
File "/robot/install/hardware/lib/hardware/big_bird_4_0_capcom", line 8, in <module>
sys.exit(main())
File "/robot/install/node_helpers/lib/python3.10/site-packages/node_helpers/spinning/initialization.py", line 68, in spin_fn
rclpy.spin(node, executor)
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/__init__.py", line 226, in spin
executor.spin_once()
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 794, in spin_once
self._spin_once_impl(timeout_sec)
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 775, in _spin_once_impl
handler, entity, node = self.wait_for_ready_callbacks(
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 711, in wait_for_ready_callbacks
return next(self._cb_iter)
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 517, in _wait_for_ready_callbacks
waitables.extend(filter(self.can_execute, node.waitables))
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 457, in can_execute
return not entity._executor_event and entity.callback_group.can_execute(entity)
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/callback_groups.py", line 102, in can_execute
with self._lock:
SystemError: attempting to create PyCFunction with class but no METH_METHOD flag
Example 2:
In this case, it happened when calling is_cancel_requested property on a ServerGoalHandle
Traceback (most recent call last):
File "/robot/install/node_helpers/lib/python3.10/site-packages/node_helpers/robust_rpc/_wrappers.py", line 72, in wrapper
return callback(goal)
File "/robot/install/node_helpers/lib/python3.10/site-packages/node_helpers/actions/server/base_handler.py", line 91, in _on_goal_with_report
result = self.on_goal(goal_handle)
File "/robot/install/node_helpers/lib/python3.10/site-packages/node_helpers/actions/server/fail_fast_handler.py", line 54, in on_goal
return super().on_goal(goal_handle)
File "/robot/install/node_helpers/lib/python3.10/site-packages/node_helpers/actions/server/base_handler.py", line 71, in on_goal
return worker.execute_callback(self._request_timeout)
File "/robot/install/node_helpers/lib/python3.10/site-packages/node_helpers/actions/server/worker.py", line 82, in execute_callback
while timeout_obj and not self.goal_handle.is_cancel_requested:
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/action/server.py", line 98, in is_cancel_requested
return GoalStatus.STATUS_CANCELING == self.status
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/action/server.py", line 102, in status
with self._lock:
SystemError: attempting to create PyCFunction with class but no METH_METHOD flag
Additional information
This happens a few times a day, on a single machine running ros2 and ~25-50 nodes.
The text was updated successfully, but these errors were encountered:
Bug report
Required Info:
Steps to reproduce issue
WIP. Need some help isolating why this might be happening so I can create reproducible example. This issue is to get the conversation started, and see if others have seen something similar in the wild.
Expected behavior
No exception
Actual behavior
Occasional failures. Here are 2 examples of Tracebacks we've had happen on our robots, in the wild:
Example 1
Example 2:
In this case, it happened when calling
is_cancel_requested
property on a ServerGoalHandleAdditional information
This happens a few times a day, on a single machine running ros2 and ~25-50 nodes.
The text was updated successfully, but these errors were encountered: