Change all read_only parameters to false to avoid issues when using s… #973
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to the issue reported: #966
We need to change all the read_only to false for the moment to avoid issues when using spawners with parameter file. The read-only parameters cannot be loaded as they are expected to exist at the startup of the LifeCycle node. Spawners tend to load the passed parameter files before configuring the controllers.
The above deduction is made from the following references:
http://design.ros2.org/articles/qos_configurability.html#read-only-parameters
https://docs.ros.org/en/galactic/Tutorials/Beginner-CLI-Tools/Understanding-ROS2-Parameters/Understanding-ROS2-Parameters.html#ros2-param-load
@christophfroehlich @bmagyar It would be great to get your insight on this