Preserve planner-specific MoveGroup failure codes in /move_action#3699
Open
eclipse0922 wants to merge 3 commits intomoveit:mainfrom
Open
Preserve planner-specific MoveGroup failure codes in /move_action#3699eclipse0922 wants to merge 3 commits intomoveit:mainfrom
eclipse0922 wants to merge 3 commits intomoveit:mainfrom
Conversation
|
Please target the |
c1f3e31 to
64c3d6c
Compare
nbbrooks
approved these changes
Mar 8, 2026
Contributor
nbbrooks
left a comment
There was a problem hiding this comment.
thank you for the contribution!
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3699 +/- ##
==========================================
- Coverage 46.24% 0.00% -46.23%
==========================================
Files 726 51 -675
Lines 59483 5938 -53545
Branches 7624 1057 -6567
==========================================
- Hits 27504 0 -27504
+ Misses 31813 5938 -25875
+ Partials 166 0 -166 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Author
|
@nbbrooks How do I execute CI? |
This file contains hidden or 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
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.
Summary
Preserve planner-specific non-success
MoveItErrorCodesin/move_actionplan-only execution instead of always collapsing them to genericFAILURE(99999).Root cause
planning_pipeline->generatePlan(...)returnsfalsefor any non-success planner result. InMoveGroupMoveAction::executeMoveCallbackPlanOnly, thatfalsereturn currently overwritesres.error_code.valwithMoveItErrorCodes::FAILUREeven when the planner already set a more specific non-success code such as:INVALID_GROUP_NAME(-15)NO_IK_SOLUTION(-31)That destroys information that downstream action clients need for correct diagnosis and handling.
Change
Only fall back to generic
FAILUREwhen the current code is stillSUCCESSorUNDEFINED. If the planner already populated a specific non-success code, preserve it and log that preservation.Validation
Validated downstream against
jazzy/ MoveIt2.12.4in a live Isaac ROS cuMotion integration harness.Observed before this patch:
-31-31/move_actionstill returned generic99999Observed after this patch:
/move_actionpreserved the original planner-specific failure code (-31)This also matches the user-visible symptom reported in #3667 where invalid group or unreachable goals lose their original error code and appear as generic failure.
Related
Refs #3667