Open firesurfer opened 1 year ago
This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.
Just to avoid having this issue closed due to being stale and in order to help anyone who runs into the same issue.
A possible workaround is to set the loglevel of the corresponding logger to Error:
rclcpp::get_logger("moveit_ros.planning_scene_monitor.planning_scene_monitor").set_level(rclcpp::Logger::Level::Error);
Just be warned that this might also hide other warnings!
This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.
Description
The same as https://github.com/ros-planning/moveit/issues/1398
Happens also with moveit2. Only difference is that disableing the internal octomap doesn't seem to make any difference.
Your environment
Steps to reproduce
I publish a helper tf frame at some point of time that I use for some manipulation tasks. This frame is not published anymore after my manipulation work is done.
Move it then starts spamming these warnings even though I do not issue any new planning request that have that frame involved:
Expected behaviour
No warning should be printed if frame is not published anymore but also not used