-
Notifications
You must be signed in to change notification settings - Fork 287
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
Fields selection #354
Comments
Can you please provide a copy of your source to reproduce the problem? |
Here is a repo with the different workspaces (ros1_bridge as submodule) Thanks for your reply |
@amifsud I've managed to reproduce your problem, but only under certain conditions. If I run the commands you have given in sequence in a single terminal, I can reproduce your behaviour. However, if I run them in three separate terminals, one for each of the three workspaces, then the bridge builds correctly and behaves correctly. Please try running the commands in three terminals like this: In terminal 1:
In terminal 2:
In terminal 3:
ROS 1 and ROS 2 workspaces are not meant to be overlayed on each other (the |
Hello, I didn't mention in the first post that it was actually in different terminals, sorry for that. I tested again today, I got the same issue. Thanks, |
I actually could reproduce even in three separate terminals. Which branch of |
@amifsud Opened a PR for this issue too. Please test it (using quarkytale/parsing_ros2_msg_fields branch) with your project if you get a chance! |
Bug report
Required Info:
Operating System: Ubuntu 20.04
Installation type: Binaries, ros1_bridge from sources
Version or commit hash: Foxy HEAD
DDS implementation: Compile time issue
Steps to reproduce issue
Trying to map the following messages in ros1:
Example.msg :
Example1.msg :
to those ones in ros2:
Example2.msg :
Example3.msg :
With the mapping rules :
Or the following ones :
In ros1 workspace (~/ros1_ws):
In ros2 workspace (~/ros2_ws):
In ros1_bridge workspace (~/bridge_ws):
Expected behavior
In ros1 workspace (~/ros1_ws):
Result :
Result :
In ros2 workspace (~/ros2_ws):
Result :
Result :
In ros1_bridge workspace (~/bridge_ws):
Result : No error or warning for both mapping rules
Result : for both mapping rules :
Actual behavior
Expected behavior until in ros1_bridge workspace.
In ros1_bridge workspace (~/bridge_ws):
Result:
Expected behavior for the first mapping rules.
For the second mapping rule (field selection to the right)
Result:
Expected behavior for the first mapping rules.
For the second :
Additional information
I tried to use field_2_to_1 to take field selection always to the left, but I got another problem (see this issue).
The text was updated successfully, but these errors were encountered: