Skip to content
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

Merged

Conversation

saikishor
Copy link
Member

@saikishor saikishor commented Jan 5, 2024

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

Copy link

codecov bot commented Jan 5, 2024

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (64c9e2a) 47.89% compared to head (7ae58d8) 47.87%.

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     
Flag Coverage Δ
unittests 47.87% <0.00%> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
controller_manager/src/controller_manager.cpp 39.15% <0.00%> (-0.07%) ⬇️

@saikishor saikishor marked this pull request as ready for review January 5, 2024 15:04
Copy link
Contributor

@olivier-stasse olivier-stasse left a 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.

Copy link

@dyackzan dyackzan left a 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

@saikishor saikishor added the backport-iron This label should be used by maintaines only! Label triggers PR backport to ROS2 Iron. label Jan 6, 2024
@bmagyar bmagyar merged commit bdad009 into ros-controls:master Jan 8, 2024
14 checks passed
mergify bot pushed a commit that referenced this pull request Jan 8, 2024
…e manager (#1271)

(cherry picked from commit bdad009)

# Conflicts:
#	controller_manager/src/controller_manager.cpp
bmagyar pushed a commit that referenced this pull request Jan 8, 2024
HovorunB added a commit to pixel-robotics/ros2_control that referenced this pull request Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-iron This label should be used by maintaines only! Label triggers PR backport to ROS2 Iron.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Loading robot_description from topic does not work as expected
4 participants