ros2

Hi all,

I have looked into the marker example and according to the description in line 47, the commands from line 47-63 should modify the existing marker. However in reality, new markers are created.

Reason is the id 0 that is being set for the first marker: [this line](https://github.com/osrf/gaze

Hi,

I figured I'd ask and see if there was interest in something like this. In order to help remove salt and pepper noise from images, typically you might use dilation and erosion. The same concept could apply to navigation2 costmap layers, where an erroneous voxel layer or obstacle layer measurement (or static layer with SLAM session and things moving around) would make in the middle of free s

Brief feature description

We should use cxx::function instead of cxx::function_ref in the cxx::unique_ptr. But when we do the transition it is likely that the custom deleter classes will remain since they will also work with cxx::function. This should be cleaned up since they are no longer required.

1. Replace cxx::function_ref with cxx::function
2. Remove custom deleter clas

As which has been done in rqt_plot

Now that zenohd can be configured via a configuration file, we should provide a default one in /etc/zenohd/.
The zenohd service will use it.

Desired behavior

There are functions inside the visualization capabilities plugin that could be generally useful for other plugins, for exa

I propose to extend the minimal robot from the ros2_control_test_assets with transmission tags too. This should be then used for testing of transmissions.

The idea is to have one fully-featured URDF for doing main test of different features. Although not all tags will be used in all tests, they all have to be parsable and should not collide with each other. This can be only achieved if we rea