-
Notifications
You must be signed in to change notification settings - Fork 201
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
Port tf2 ros message filter with ros2 tf2 and message filters #81
Conversation
- add ros2 package dependencies and rules - remove boost with std functions instead - use rclcpp Time and Duration - remove APIs to node callback queue due to no callback queue in ros2 now - Change failure callback register with failure prompting due to no corresponding boost signal2 in C++11 and later - Fix expected transform count in case of time tolerance - Adapt to ros2 tf2 APIs
@tfoote - we would like to get this one and the linked dependency merged in time for the Crystal release, as these are dependencies for the ROS2 Navigation which we're targeting for Crystal (as you already know). Please let us know if that can be done in time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to be reformatted to reduce the diffs and make it easier to review. There is also a potential for races with the removal of locks which needs to either be fixed, or at the very least have a comment saying why they are safe to remove.
@clalancette - please review again. Our Navigation team is depending on this for the Crystal release. Thanks! |
Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a couple of more things that I noticed this time through the review. There are also a couple of nits that I'll push a patch for in a few minutes. We are close enough here that I'm going to run CI on it, but before we can merge we need to fix, or at least have answers for, the couple of things in the review.
This added 2 new warning on windows: https://ci.ros2.org/job/ci_windows/5476/warnings43Result/new/ @clalancette did you have those quick patches you mentioned? |
I already pushed it in 6282609 |
Thanks @clalancette sorry I was looking for commits after your comment. |
…s about downgrading a size_t.
It is commented out since we don't have underlying support for it, with a TODO for the future. Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small nit, looks like you are over-including/over-linking here. I believe this was there before you worked on it, but it would be a good time to remove it.
Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm generally good with this change now. @tfoote thinks he has found the issue with the failed link on macOS, so once we have that fixed we can run CI again and then hopefully approve and merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with CI.
I think that this will resolve the linking issue. Instead of adding an export for the library it turns out I don't think it's necessary: ros2/message_filters#17 |
Here's a CI run incorporating ros2/message_filters#17: Updated build numbers for crashed agents. |
It requires another PR ros2/message_filters#13 of ros2
message filter
to work.