ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I noticed that too, but did not find the time to debug it yet. This is the relevant commit: https://github.com/ros-planning/moveit/commit/492e8816c5385880a99486765e958a98d11e3df2
To the best of my current knowledge the error message does not change any behavior of the node though, but I'm not 100% sure.
Apparently some code in the PlanAndExecute
pipeline uses the RobotStateMsg -> RobotState
conversion tools without checking whether the message is actually filled in.
Anything I can do?
You could track down when and where this happens and file an issue on the github project. That would (hopefully) help a lot.
2 | No.2 Revision |
I noticed that too, but did not find the time to debug it yet. This is the relevant commit: https://github.com/ros-planning/moveit/commit/492e8816c5385880a99486765e958a98d11e3df2
To the best of my current knowledge the error message does not change any behavior of the node though, but I'm not 100% sure.
Apparently some code in the PlanAndExecute
pipeline uses the RobotStateMsg -> RobotState
conversion tools without checking whether the message is actually filled in.
Anything I can do?
You could track down when and where this happens and file an issue on the github project. That would (hopefully) help a lot.
--- EDIT ---
By now, this should be fixed upstream. See https://github.com/ros-planning/moveit/pull/589 .