-
Notifications
You must be signed in to change notification settings - Fork 337
Remove the dangling param flag for robot_description with parameter #2115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the dangling param flag for robot_description with parameter #2115
Conversation
@lukicdarkoo we have deprecated the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't support robot_description from parameters any more, but this improves robustness
@christophfroehlich We just pass all arguments to the controller manager: We use it for some other purposes before passing it to the controller manager. Alternatively, we can remove the But in any case, if the user passes the |
@saikishor should we add a test for that to prevent that in the future? 🤷♂️ |
I was relying on the tests from ros2_control_demos🙈 |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2115 +/- ##
==========================================
- Coverage 89.30% 89.29% -0.02%
==========================================
Files 139 139
Lines 15500 15502 +2
Branches 1318 1318
==========================================
- Hits 13843 13842 -1
- Misses 1154 1156 +2
- Partials 503 504 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Tested, it works! Thank you! |
d7b0af6
into
ros-controls:master
Fixes #2082 (comment)
Initially, when we suppressed the warning we only handled the case of the robot_description parsed using topics but not the parameter.
@lukicdarkoo Can you check this change and let us know :)