Tomoya Fujita

No, i do not think anybody working on this. feature sounds good to me, but it could not be so straight-forward. currently it knows which node to set the parameters...

@llapx requesting your review, since you are original author on this change.

CI: * Linux [](http://ci.ros2.org/job/ci_linux/17615/) * Linux-aarch64 [](http://ci.ros2.org/job/ci_linux-aarch64/12158/) * Windows [](http://ci.ros2.org/job/ci_windows/18185/)

https://ci.ros2.org/job/ci_windows/18185/cmake/new/ is unrelated.

I think that this is expected behavior for ros2 daemon, it is well described [what-is-ros2-daemon](https://answers.ros.org/question/327348/what-is-ros2-daemon/).

Ah, i see. you are saying > But this cache is getting outdated and only restarting the daemon fixes it. problem-1: old cache can be seen, and will not be...

could be related to https://github.com/ros2/rmw_fastrtps/pull/514 if the communication is localhost?

@BrettRD if your problem is related to https://github.com/ros2/rmw_fastrtps/pull/514, it would be really appreciated to try https://github.com/ros2/ros2/tree/foxy branch to check if you still meet the problem.

i think that sounds okay, and whole procedure is https://docs.ros.org/en/foxy/Installation/Linux-Development-Setup.html. i usually use `ubuntu:20.04` docker container as base.

> I'm not sure why rmw could cause this problem, does changing rmw would solve this issue? discovery protocol is implemented in RMW implementation, so changing rmw would solve the...