-
Notifications
You must be signed in to change notification settings - Fork 434
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
print warning if event callback is not supported instead of passing e… #2648
Conversation
…xception. Signed-off-by: Tomoya Fujita <Tomoya.Fujita@sony.com>
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.
RCLCPP_DEBUG( | ||
RCLCPP_WARN( | ||
rclcpp::get_logger("rclcpp"), | ||
"Failed to add event handler for incompatible qos; wrong callback type"); | ||
"Failed to add event handler for incompatible qos; not supported"); |
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 warning
is more appropriate here, this is more visible for user that the callback type is not supported with this rmw implementation. besides, message is wrong, that is just not supported.
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 is a much better solution! Thanks @fujitatomoya
Pulls: #2648 |
…xception.
replaces #2644
rmw_zenoh
) might not support those publisher / subscription event callbacks. I think that is okay to returnUNSUPPORTED
from RMW implementation. (RMW implementation does not have to support all RMW interfaces.)rmw_zenoh
can generate the exception butrmw_fastrtps
, this situation should be avoided.)