Skip to content

Conversation

@mergify
Copy link

@mergify mergify bot commented Mar 25, 2025

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.

@mergify mergify bot added the conflicts label Mar 25, 2025
@mergify
Copy link
Author

mergify bot commented Mar 25, 2025

Cherry-pick of 98952b5 has failed:

On branch mergify/bp/jazzy/pr-449
Your branch is up to date with 'origin/jazzy'.

You are currently cherry-picking commit 98952b5.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   launch_ros/launch_ros/actions/lifecycle_node.py
	both modified:   launch_ros/launch_ros/actions/load_composable_nodes.py

no changes added to commit (use "git add" and/or "git commit -a")

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

@christophebedard
Copy link
Member

Pulls: #453
Gist: https://gist.githubusercontent.com/christophebedard/ad28ca56666edb2c62944e4fd6d2f98b/raw/d37b83ee0706759bb664be4be9d14666241f252b/ros2.repos
BUILD args: --packages-above-and-dependencies launch_ros test_launch_ros
TEST args: --packages-above launch_ros test_launch_ros
ROS Distro: jazzy
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/15458

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Linux-rhel Build Status
  • Windows Build Status

@christophebedard
Copy link
Member

I included #438 (the backport of #430) in this PR (the backport of #449, which fixes an issue with #430). So the CI above tests both. Then we can merge #438 and #453. See #438 (comment).

@christophebedard
Copy link
Member

The ros2bag test failure on Windows is known: ros2/rosbag2#1947.

CI with both PRs looks good, so I'll merge one after the other, making sure that this one gets properly rebased.

Signed-off-by: Steve Macenski <stevenmacenski@gmail.com>
(cherry picked from commit 98952b5)
@christophebedard christophebedard force-pushed the mergify/bp/jazzy/pr-449 branch from a248415 to 0d42877 Compare March 25, 2025 04:01
@christophebedard
Copy link
Member

@christophebedard christophebedard merged commit f4b97c1 into jazzy Mar 25, 2025
2 checks passed
@christophebedard christophebedard deleted the mergify/bp/jazzy/pr-449 branch March 25, 2025 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants