Skip to content
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

Lifecycle nodes silently swallow exception information on failed transition. #776

Closed
rotu opened this issue Jul 3, 2019 · 1 comment
Closed

Comments

@rotu
Copy link
Contributor

rotu commented Jul 3, 2019

Bug report

Required Info:

  • Operating System:
    • Ubuntu 18
  • Installation type:
    • From source
  • Version or commit hash:
  • DDS implementation:
    • OpenSplice
  • Client library (if applicable):
    • rclcpp

Steps to reproduce issue

With navigation2 stack installed in one window:

ros2 run nav2_map_server map_server     

in another window::

ros2 run nav2_map_server map_server

Expected behavior

An error message is logged containing verbose error information.

Actual behavior

The following is logged:

ros2 run nav2_map_server map_server
[INFO] [map_server]: Creating
[INFO] [map_server]: Configuring
[WARN] []: Error occurred while doing error handling.
[FATAL] [map_server]: Lifecycle node entered error state

Additional information

This is upstream of the issue: ros-navigation/navigation2#881
As explained by @crdelsey, it seems the code to verbosely log the exception exists but is commented out:

// TODO(karsten1987): Windows CI doesn't let me print the msg here
// the todo is to forward the exception to the on_error callback
// RCUTILS_LOG_ERROR("Caught exception in callback for transition %d\n",
// it->first);
// RCUTILS_LOG_ERROR("Original error msg: %s\n", e.what());
// maybe directly go for error handling here
// and pass exception along with it

@rotu
Copy link
Contributor Author

rotu commented Jul 19, 2019

fixed by #777

@rotu rotu closed this as completed Jul 19, 2019
nnmm pushed a commit to ApexAI/rclcpp that referenced this issue Jul 9, 2022
It should not fini its output argument, silently invalidating the given pointer.

Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
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

No branches or pull requests

1 participant