-
Notifications
You must be signed in to change notification settings - Fork 935
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
Add debugging informative log statement for a common error #2509
Add debugging informative log statement for a common error #2509
Conversation
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.
👍
not sure if you want to include the group name as well?
Codecov Report
@@ Coverage Diff @@
## master #2509 +/- ##
==========================================
+ Coverage 56.68% 60.24% +3.57%
==========================================
Files 281 351 +70
Lines 25455 26475 +1020
==========================================
+ Hits 14426 15948 +1522
+ Misses 11029 10527 -502
Continue to review full report at Codecov.
|
sure, why not. I've added dded the group name. Thanks for the speedy approve! |
add debugging informative log statement for a common error Co-authored-by: Peter Mitrano <pmitrano@armstorm>
add debugging informative log statement for a common error Co-authored-by: Peter Mitrano <pmitrano@armstorm>
add debugging informative log statement for a common error Co-authored-by: Peter Mitrano <pmitrano@armstorm>
Description
If the user calls setJointValueTarget with the wrong number of joint values, it just returns false without providing any information as to what went wrong. Personally when something in moveit goes wrong the first thing I do is turn on debug logging so this would help in that case.
Checklist