-
Notifications
You must be signed in to change notification settings - Fork 311
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
Initialize the controller manager services after initializing resource manager #1271
Initialize the controller manager services after initializing resource manager #1271
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1271 +/- ##
==========================================
- Coverage 47.89% 47.87% -0.03%
==========================================
Files 41 41
Lines 3451 3453 +2
Branches 1876 1878 +2
==========================================
Hits 1653 1653
Misses 444 444
- Partials 1354 1356 +2
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.
Looks good to me.
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.
Pulled and tested these changes into my humble setup and saw my issues resolved as discussed in: #1262
… resource manager (backport ros-controls#1271) (ros-controls#1278)" This reverts commit 9387936.
Exposing CM services before initializing the resource manager might be a bad idea as the spawners might trigger the controller activation even before the actual system is ready. Exposing it later, might avoid such issues
Fixes #1262