Closed amifsud closed 2 years ago
Can you please provide a copy of your source to reproduce the issue?
Here is a repo with the different workspaces (ros1_bridge as a submodule)
Thanks again for your reply Alexis
Thanks for sharing the source code. I could reproduce both #353 and #354. Looking into it.
@amifsud Please see this comment on #354. I believe this issue has the same cause. Try running the commands in three separate terminals.
Hello,
As I said in #354, I actually used different terminals.
Thanks, Alexis
@amifsud I think this might solve your issue, please try again using quarkytale/mapping_rule branch of ros1_bridge
. It should print out using both mapping rules. Let me know how it goes!
@quarkytale Yes it is working for both mapping rules. Thanks !
Thanks for trying it out! I'll open a PR for it to be merged into master.
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 message in ros1:
Example.msg :
to this one in ros2:
Example1.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 :
In ros2 workspace (~/ros2_ws):
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: For the second mapping rule (using field_2_to_1)
Expected behavior for the first.
Result: Empty answer for the second mapping rule, expected behavior for the first.