Felix von Drigalski

Sorry that this has been left sitting for so long. Have you been able to solve this? It looks like your roscore process might have restarted and your nodes can't...

I don't think it would see much use, so I wouldn't bother. Personally I've never changed those parameters (except for STOMP), I suspect that >99% of people won't try to...

It seems like the tests in the failing test pipeline all end like this: ``` ... shutting down processing monitor complete [ROSTEST]rostest teardown /home/runner/work/moveit/moveit/.work/target_ws/src/moveit/moveit_ros/move_group/test/test_check_state_validity_in_empty_scene.test complete ]]><![CDATA[ [31m[check_state_validity_in_empty_scene-4] process has died...

I updated the original post.

The build fails because of clang-tidy, which somehow fails to work correctly in my container. I'll try to figure this out tomorrow. > @tylerjw I do think the new codecov...

Rebased to get rid of the codecov errors

Ping

I am all for this - in fact, it already [exists in Python](https://docs.ros.org/en/api/moveit_commander/html/planning__scene__interface_8py_source.html#l00163) and the function should be linked if a C++ implementation is added.

The politically correct term is always „workaround“ :) On Mon, Dec 14, 2020 at 17:30 Simon Schmeisser wrote: > Oh and don't use the word "hack" in commit messages ......

You can fork [this project](https://ros-planning.github.io/moveit_tutorials/) and submit a pull request when you are ready.