rqt_cm: Fix handling of unconfigured controllers during spawn action (backport #1794) #1798
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.
Description:
This PR addresses an #1791 issue where controllers in the "unconfigured" state were being loaded rather than configured during the action_spawn process. The previous behavior could lead to errors when attempting to activate controllers that were not yet configured.
Changes made:
Testing:
I was unable to test the changes with
diffbot.launch.py
due to build issues withros2_controllers
on my system running ROS Iron, as therolling
build is not compatible withiron
.This is an automatic backport of pull request #1794 done by [Mergify](https://mergify.com).