-
Notifications
You must be signed in to change notification settings - Fork 227
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
add support for lazy subscribers #272
add support for lazy subscribers #272
Conversation
Also, not sure if rolling or ros2 is the right branch - they appear to be even with one another right now... |
Yeah, it is a bit messy now. |
@clalancette so this can't go into Iron - but can it get merged into rolling now, or does it have to wait until some certain milestone between the Iron and J-turtle release? |
Rolling is completely open for business! |
any updates here ? |
@ahcorde - this is basically waiting on a review from a maintainer (I've fully implemented the downstream stuff for image_proc and depth_image_proc, so I'm confident this is all we need to add) |
This implements #780 for ROS 2 distributions after Iron, where we have: * Connect/disconnect callbacks, per ros2/rmw#330 (this made it into Iron) * Updated APIs in ros-perception/image_common#272 (this is only in Rolling currently)
This implements ros-perception#780 for ROS 2 distributions after Iron, where we have: * Connect/disconnect callbacks, per ros2/rmw#330 (this made it into Iron) * Updated APIs in ros-perception/image_common#272 (this is only in Rolling currently)
This implements #111 for releases after Iron (where we have connect/disconnect callbacks, per ros2/rmw#330)