Tomoya Fujita

> @VictorLamoine could you add QoS improvement in this PR? this has been addressed by https://github.com/ros2/ros2cli/pull/970

@VictorLamoine can you close this one, instead i will come up with documentation described in https://github.com/ros2/ros2cli/issues/843#issuecomment-2716401376. if you can review, that would be appreciated.

@mauropasse as you mentioned, it seems that it should be good enough with `reliable` so that client will not miss the status from the server once goal request begins. >...

i am happy to, but cannot promise when. probably i can do that with my spare time. > Or we can add a good first issue label to see if...

@navaneeth-dev thanks for the contribution. > I noticed we are using yarn any plans to migrate to pnpm or something? i am not familiar with pnpm but i would create...

@kjjpc thanks for posting the issue and detailed report. > return [lc_node, emit_configure, emit_active] as a possible work-around, changing this line into `return [lc_node, emit_active, emit_configure]` can mitigate the issue...

I think it would be nice to print more details of rmw implementation for practice, this would be really helpful to understand the environment for debugging instead of asking questions....

@rursprung I had a chat about this with other developers. what we could do is that develop ros2doctor plugin subcommand and get the user specific (or rmw specific) information instead...

@mjcarroll i might be mistaken, but i was thinking opposite... > The main concern is that if you had a late-joining lifecycle node, that it could be transitioned inadvertently by...

i only can think of the usage with DDS based RMW implementation. even after `rcl_shutdown` is called, DDS participants are still active, so that all entities under that participants such...