feat(autoware.repos): bumped the cuda_blackboard's version to 0.2.0 #5924
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.
Description
In the
cuda_blackboard
subscribers needed to configure whether they need or not a compatible subscriber (a default ROS message), causing confusion as to when that was necessary. In thev0.2.0
release, the compatible subscriber is added by default and disconnected automatically once a negotiated (a cuda blackboard) publisher is detected.How was this PR tested?
Tested locally using the logging simulator with the PRs from autowarefoundation/autoware_universe#9722
Notes for reviewers
This PR does not make an impact in the current autoware.
However, it is required to address the feedback received in autowarefoundation/autoware_universe#9453
Effects on system behavior
Nodes using the
cuda_blackboard
will be able to automatically disconnect to the compatible subscriber once a negotiated subscriber message is received.