-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Add backward_ros dependency #5404
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
base: main
Are you sure you want to change the base?
Add backward_ros dependency #5404
Conversation
Signed-off-by: Sushant Chavan <gitecsvc@gmail.com>
4d3d62d
to
1389e07
Compare
@Sushant-Chavan, your PR has failed to build. Please check CI outputs and resolve issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Two questions:
- How does this look when a crash occurs? Can you cause one on a normal
nav2_bringup
composed bringup and let me know (a) the logging output (b) what do the other servers react to it - Did you do any perf testing to check on the runtime difference on this addition? Anything appreciable?
Sorry, this PR was meant to be for my fork. Unfortunately I didnt realize that I created an upstream PR until you reviewed it 😞 I am yet to test it properly, so setting this PR as a draft for now. But I realized that using backward_ros with composed node will not work and there is already an open issue in rclcpp for addressing this. I will perform some tests without node composition and re-request a review with the details you requested :) |
I was able to do some tests to see the effects of using backward_ros. I updated the PR description with details of the same, along with answers to your questions :)
The behavior of other servers was exactly the same in both cases as can be seen in the app logs. |
Pull in
I think adding these instructions to https://docs.nav2.org/tutorials/docs/get_backtrace.html for the backward ros section is important context to add. What happens if we don't use
Whats your sense on the likelihood of this being completed? |
Basic Info
Description of contribution in a few bullet points
RelWithDebInfo
orDebug
configurations. See sample output belowDescription of how this change was tested
plan_publisher_
shared pointer right before publishing the global plan in thePlannerServer::publishPlan()
RelWithDebInfo
configurationuse_composition
flag set to false, using the command:ros2 launch nav2_bringup tb3_simulation_launch.py headless:=False use_composition:=false
Logs without backward_ros dependency
Logs with backward_ros dependency
Future work that may be required in bullet points
None
For Maintainers:
backport-*
.