You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With #459 merged in, a user is able to provide a callback for when an participant on the topic is discovered but unable to be matched due to incompatible QoS policies. This feature request is for leveraging this feature even when a user does not provide a custom callback function, by setting a default callback function that prints a warning (initially suggested at ros2/ros2#822 (comment)) on the discovery of an incompatible participant on the topic.
Implementation considerations
What should the behavior be if the underlying middleware does not support this kind of QoS event callback?
The text was updated successfully, but these errors were encountered:
Feature request
Feature description
With #459 merged in, a user is able to provide a callback for when an participant on the topic is discovered but unable to be matched due to incompatible QoS policies. This feature request is for leveraging this feature even when a user does not provide a custom callback function, by setting a default callback function that prints a warning (initially suggested at ros2/ros2#822 (comment)) on the discovery of an incompatible participant on the topic.
Implementation considerations
What should the behavior be if the underlying middleware does not support this kind of QoS event callback?
The text was updated successfully, but these errors were encountered: