Skip to content

Return NODE_NAME_NON_EXISTENT instead of ERROR. - #44

Merged
eboasson merged 1 commit into
ros2:masterfrom
evshary:modify_ret_value
Sep 24, 2019
Merged

Return NODE_NAME_NON_EXISTENT instead of ERROR.#44
eboasson merged 1 commit into
ros2:masterfrom
evshary:modify_ret_value

Conversation

@evshary

@evshary evshary commented Sep 24, 2019

Copy link
Copy Markdown
Contributor

There are some return value errors in CI test of rcl and rclaction, like this.

I think we should have the return value RMW_RET_NODE_NAME_NON_EXISTENT if we can't get the node.

Signed-off-by: evshary evshary@gmail.com

Signed-off-by: evshary <evshary@gmail.com>
@eboasson

Copy link
Copy Markdown
Collaborator

I agree — see also ros2/rmw#182, ros2/rmw_opensplice#281 and ros2/rmw_fastrtps#311.

@eboasson
eboasson merged commit a61a014 into ros2:master Sep 24, 2019
@dirk-thomas

Copy link
Copy Markdown
Member

I would expect you to need separate branches for this. The master branch will work with the master branches of ROS 2 but e.g. for Dashin this won't work since this new error code isn't available in Dashing (and I would expect it not being backported).

@eboasson

Copy link
Copy Markdown
Collaborator

Oops. Thanks for warning me, @dirk-thomas. Clearly I'm not quite used to tracking moving targets yet — which is quite strange for someone who once worked for a radar company.

Methinks #45 should solve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants