-
Notifications
You must be signed in to change notification settings - Fork 237
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
Create a default warning for qos incompatibility #536
Merged
ivanpauno
merged 6 commits into
ros2:master
from
aws-ros-dev:emersonknapp/default-incompatible-qos-callback
Apr 15, 2020
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
4c13f0e
Create a default warning for qos incompatibility
emersonknapp 3ad1c35
Cleanup names
emersonknapp 7c7b6c7
add tests
mm318 ef981d7
fix unit test failures
mm318 f56ff54
synchronize with rclcpp PR comments
mm318 8ea55cf
address PR comments
mm318 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 fine, though I think that a bit unnecessary.
IMO, a nicer approach would have been the following:
In both cases the result the user sees is the same, so I won't block on the change.
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 thought about doing the way you mentioned, but with
event_callbacks.incompatible_qos
no longerNone
, it's harder to determine later on if it's the default one or a user provided one, which is needed to handle theUnsupportedEventTypeError
exception differently.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.
It could initially be
None
, except the user provided explicitly one.If it's set to
None
and usedefault_callbacks
is true, the event is registered with the default callback when the publisher is created.I think the approach I'm mentioning is exactly the one used in
rclcpp
.