-
Notifications
You must be signed in to change notification settings - Fork 304
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
Fix unload of controllers when spawned with --unload-on-kill
#1717
Fix unload of controllers when spawned with --unload-on-kill
#1717
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1717 +/- ##
==========================================
+ Coverage 86.73% 86.75% +0.02%
==========================================
Files 116 116
Lines 10618 10628 +10
Branches 978 980 +2
==========================================
+ Hits 9209 9220 +11
+ Misses 1058 1057 -1
Partials 351 351
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
LGTM
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.
Thank you!
(cherry picked from commit 9e57adf) # Conflicts: # controller_manager/controller_manager/spawner.py # controller_manager/test/test_spawner_unspawner.cpp
(cherry picked from commit 9e57adf) # Conflicts: # controller_manager/test/test_spawner_unspawner.cpp
#1843) Co-authored-by: Sai Kishor Kothakota <sai.kishor@pal-robotics.com>
#1842) Co-authored-by: Sai Kishor Kothakota <sai.kishor@pal-robotics.com>
Fix the bug, when using
--unload-on-kill
option, the spawner only unloads the last controller instead of all the controllers. This PR proposes a solution to fix the above issue