Skip to content

Lifecycle support 2#67

Merged
mjcarroll merged 10 commits intoros:ros2from
SteveMacenski:lifecycle_support_2
Sep 1, 2020
Merged

Lifecycle support 2#67
mjcarroll merged 10 commits intoros:ros2from
SteveMacenski:lifecycle_support_2

Conversation

@SteveMacenski
Copy link
Copy Markdown
Member

@SteveMacenski SteveMacenski commented Jul 29, 2020

Supersedes #64 to:

  • Enable lifecycle nodes in ROS2
  • Fix ROS2 porting issues
  • Fix ROS2 WaitUntilXYZ() functions with spins on nodes already spinning (requirement for this to work)
  • Tested to be actualy working now & integrated into Nav2
  • No reduced capability
  • Removes a number of crashing problems introduced in porting

@SteveMacenski
Copy link
Copy Markdown
Member Author

SteveMacenski commented Jul 30, 2020

Whoops, see the commit f72af40, I didn't push it to remote, I had already done that :-)

@SteveMacenski
Copy link
Copy Markdown
Member Author

Pinging @mjcarroll as listed maintainer, can we get a review?

This work has been merged in and used on nav2 for about a week now without any issues. I think this is safe for a review for inclusion

@SteveMacenski
Copy link
Copy Markdown
Member Author

Pinging @mjcarroll

@mjcarroll
Copy link
Copy Markdown
Member

Pong. I'm reviewing.

Copy link
Copy Markdown
Member

@mjcarroll mjcarroll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, looks good, one comment about DRY and a question about a previous resolution.

@ros-discourse
Copy link
Copy Markdown

This pull request has been mentioned on ROS Discourse. There might be relevant details there:

https://discourse.ros.org/t/ros-2-tsc-meeting-minutes-2020-08-20/16063/1

@SteveMacenski
Copy link
Copy Markdown
Member Author

@mjcarroll pinging again

@mjcarroll mjcarroll merged commit 99e8e63 into ros:ros2 Sep 1, 2020
@mjcarroll
Copy link
Copy Markdown
Member

@SteveMacenski would you like this to be released into rolling?

@SteveMacenski
Copy link
Copy Markdown
Member Author

SteveMacenski commented Sep 2, 2020

I don't require it, but might be a good idea. If nothing else, having it in Foxy would be our immediate needs. Right now, we don't use Rolling in Nav2 (frankly, the emails from occasional failures in just image_pipeline is prohibitive for me to support rolling releases.).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants