Fixing lifecycle node autostart issue #445 (backport #449)#453
Fixing lifecycle node autostart issue #445 (backport #449)#453christophebedard merged 1 commit intojazzyfrom
Conversation
|
Cherry-pick of 98952b5 has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
9e76d6f to
a248415
Compare
|
Pulls: #453 |
|
The CI with both PRs looks good, so I'll merge one after the other, making sure that this one gets properly rebased. |
a248415 to
0d42877
Compare
|
Rebased. The comparison shows nothing changed: https://github.com/ros2/launch_ros/compare/a2484157e42301fa540767483df755a9201b2d9b..0d42877ca066b00ae0e8a03e5e19e9e2c93756af. |
Fixing lifecycle node autostart issue #445
The issue boils down to the emitting of signals for the first transition in the
transition_ids. It appears that sometimes the Launch system doesn't emit these in order or for whatever reason the second signal is received by the server before the first. By putting them both in a single transition, only the configure signal is emitted and activate is dependent fully on the state transition.Honestly, this is probably how it should have always been implemented, but I didn't think it mattered at the time since I thought ordering was guaranteed.
This is an automatic backport of pull request #449 done by Mergify.