-
Notifications
You must be signed in to change notification settings - Fork 229
Transform Data Callback Python #664
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
Conversation
Signed-off-by: CursedRock17 <[email protected]>
Signed-off-by: CursedRock17 <[email protected]>
clalancette
left a comment
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 think this is generally the correct thing to do here. I have a mild concern that this will cause some downstream code to break, but looking through all of the code released into rolling, nothing seems to use this in particular. I'm going to run CI on this, but @CursedRock17 can you please also open a PR to http://docs.ros.org/en/rolling/Releases/Release-Jazzy-Jalisco.html to add a note saying that we changed this?
Signed-off-by: CursedRock17 <[email protected]>
Signed-off-by: CursedRock17 <[email protected]>
Signed-off-by: CursedRock17 <[email protected]>
|
The CI should still be fine, but I forgot to update the return value in the docs |
|
I think this is good to go other than the addition to the release notes. Once that PR is open, I'll go ahead and merge this. |
This PR is meant to resolve #194 as of right now I'm working off of PR #215. We need to change
_wait_for_transform_async, to return the transform data similar to the C++ version returning aTransformStampedFuture.