-
Notifications
You must be signed in to change notification settings - Fork 299
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
Fix parameter bridge for topic if ros1 and ros2 type have a different name #177
Merged
dirk-thomas
merged 2 commits into
ros2:master
from
cyrilleberger:fix-different-msg-name
Jun 10, 2019
Merged
Fix parameter bridge for topic if ros1 and ros2 type have a different name #177
dirk-thomas
merged 2 commits into
ros2:master
from
cyrilleberger:fix-different-msg-name
Jun 10, 2019
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…fferent type name) Signed-off-by: Cyrille Berger <cyrille.berger@liu.se>
cyrilleberger
force-pushed
the
fix-different-msg-name
branch
from
March 21, 2019 09:35
4132759
to
67898df
Compare
The message printed above provides misleading information now. Please update that accordingly. |
dirk-thomas
added
in progress
Actively being worked on (Kanban column)
requires-changes
and removed
in review
Waiting for review (Kanban column)
labels
Mar 22, 2019
Do you mean the commit message? |
Sorry, I though I commented on a specific line. Without that context its not obvious. I was referring to the message printed a few lines above the change: line 69-72. |
…type Signed-off-by: Cyrille Berger <cyrille.berger@liu.se>
Is there anything else I need to change? |
dirk-thomas
added
in review
Waiting for review (Kanban column)
and removed
requires-changes
in progress
Actively being worked on (Kanban column)
labels
Jun 6, 2019
dhananjaysathe
pushed a commit
to rapyuta-robotics/ros1_bridge
that referenced
this pull request
Aug 22, 2019
… name (ros2#177) * don't specify ros1 type (it fixes the bridge if ros1 and ros2 have different type name) Signed-off-by: Cyrille Berger <cyrille.berger@liu.se> * remove ROS1 type from messages, since that type is guessed from ROS2 type Signed-off-by: Cyrille Berger <cyrille.berger@liu.se> Signed-off-by: Dhananjay Sathe <dhananjay.sathe@rapyuta-robotics.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have set ros1 type to "" since in create_bidirectional_bridge it can find out which type to use for ros1 when only specifying ros2 type.
An alternative fix would be to allow to specify different type for ros1 and ros2 in the parameters.