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
After installing ROS1 Melodic and ROS2 Eloquent, and installing ros-melodic-vision-msgs and ros-eloquent-vision-msgs,
building ros1_bridge fails with the following error:
ros1_bridge should successfully build by not associating ROS1 and ROS2 versions of vision_msgs/msg/ObjectHypothesisWithPose and vision_msgs/msg/ObjectHypothesis, as the types for the field id do not match.
Actual behavior
ros1_bridge build fails since it tries to associate ROS1 and ROS2 versions of vision_msgs/msg/ObjectHypothesisWithPose and vision_msgs/msg/ObjectHypothesis, despite the types for the field id not matching.
Additional information
ROS1 vision_msgs/msg/ObjectHypothesis uses an int64 for the id field. ROS2 vision_msgs/msg/ObjectHypothesis uses a string for the id field.
The default field matching rules, according to the docs in the repo, indicate automatic message associations are only created when all field types match.
The text was updated successfully, but these errors were encountered:
asasine
changed the title
Building ros1_bridge with vision_msgs installed (Melodic + Eloquent) fails
Building ros1_bridge with vision_msgs installed fails (Melodic + Eloquent)
Feb 16, 2022
Bug report
Required Info:
Steps to reproduce issue
After installing ROS1 Melodic and ROS2 Eloquent, and installing ros-melodic-vision-msgs and ros-eloquent-vision-msgs,
building ros1_bridge fails with the following error:
Expected behavior
ros1_bridge should successfully build by not associating ROS1 and ROS2 versions of vision_msgs/msg/ObjectHypothesisWithPose and vision_msgs/msg/ObjectHypothesis, as the types for the field
id
do not match.Actual behavior
ros1_bridge build fails since it tries to associate ROS1 and ROS2 versions of vision_msgs/msg/ObjectHypothesisWithPose and vision_msgs/msg/ObjectHypothesis, despite the types for the field
id
not matching.Additional information
ROS1 vision_msgs/msg/ObjectHypothesis uses an
int64
for theid
field. ROS2 vision_msgs/msg/ObjectHypothesis uses astring
for theid
field.The default field matching rules, according to the docs in the repo, indicate automatic message associations are only created when all field types match.
Related discussion in vision_msgs: ros-perception/vision_msgs#39
The text was updated successfully, but these errors were encountered: