Skip to content
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

Fixed errors when creating a custom subscriber. #2727

Open
wants to merge 2 commits into
base: humble
Choose a base branch
from

Conversation

bks-ol
Copy link

@bks-ol bks-ol commented Jan 19, 2025

It was impossible to create a custom subscriber inherited from rclcpp::Subscriber, I fixed this bug and added a test to check correctness.

@bks-ol bks-ol force-pushed the feature/creating_custom_sub branch from 270a517 to 52ab4b0 Compare January 19, 2025 16:16
@bks-ol bks-ol force-pushed the feature/creating_custom_sub branch from 5dbd654 to 07f410e Compare January 19, 2025 16:22
Copy link
Collaborator

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

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

i think that allowing the user application to create the custom subscription inherited from rclcpp::Subscriber would be nice.
but this PR targets to humble, and there are many test failures.

can you address that retargeting this PR against rolling that is the main development branch and all test failures?

note that, since this is breaking ABI change, we cannot backport this to already released distros that are jazzy and humble.

@bks-ol
Copy link
Author

bks-ol commented Jan 22, 2025

i think that allowing the user application to create the custom subscription inherited from rclcpp::Subscriber would be nice. but this PR targets to humble, and there are many test failures.

can you address that retargeting this PR against rolling that is the main development branch and all test failures?

note that, since this is breaking ABI change, we cannot backport this to already released distros that are jazzy and humble.

No, it doesn't break the API because there are template parameters in the function signature. There are no parameters in the internal call stack.

Please take a look:

@fujitatomoya
Copy link
Collaborator

@bks-ol ah i see, this does not change templated parameter, since it is already there.

can you address that retargeting this PR against rolling that is the main development branch and all test failures?

but this is still what we need to do to proceed this PR.

@clalancette clalancette added the more-information-needed Further information is required label Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more-information-needed Further information is required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants