feat: auto disconnect for the compatible subscriber #1
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.
As part of the review of autowarefoundation/autoware_universe#9453
It was pointed out that the selection of using or not compatible subcribers was unclear.
The reason behind that is that I had issues implementing it automatically, but in this this PR the compatible subscriber (standard ROS messages) is available by default, yet it is disabled as soon as the negotiated type (the blackboard one) is flagged as available.
This makes the
add_compatible_sub
variable ofCudaBlackboardSubscriber
deprecated and unused. To avoid breakingautoware.universe
:add_compatible_sub