Philipp Oppermann

See https://cxx.rs/binding/vec.html for the type definition of `rust::Vec`. While it's similar to a `std::vector`, it's a different type without any direction conversion. Unfortunately, I don't see any more efficient way...

To avoid the boilerplate of the `for` loop, you should be able to use [`back_inserter`](https://en.cppreference.com/w/cpp/iterator/back_inserter) together with `std::copy`. Doing a pointer copy would require a [public `set_len` method](https://github.com/dtolnay/cxx/issues/990), which is...

To make the `push_back` operation cheap you can call `reserve` with the required capacity beforehand. Then no reallocation is required anymore.

This is related to #486, right?

Issue #443 is about a SIGABRT error when running the `ros2-service-server` branch, which is not merged yet. So I don't think that this issue is related to it. > no...

Is the `ros2` command available in the terminal where you run the example?

> In case of trouble debugging, I can add the out/ folder to the CI artefact. That might gives you an easier to navigate log files. Good idea! I don't...

I did some tests on `humble` using `RMW_IMPLEMENTATION=rmw_cyclonedds_cpp`. The requests are received correctly by the service server, but the responses never reach the client for some reason.

Apparently the `Cyclone` mapping of the the `ros2-client` crate was only tested against ROS2 `galactic`, so it might not be compatible with `humble`.

> I would expect the cli to pass the latest value to the daemon and coordinator. We need to keep deployment to remote machines in mind. We probably don't want...