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
Fix the added path index vector merge in PlanningRequestAdapterChain #3464
Fix the added path index vector merge in PlanningRequestAdapterChain #3464
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## noetic-devel #3464 +/- ##
================================================
- Coverage 61.83% 61.81% -0.01%
================================================
Files 385 385
Lines 34064 34090 +26
================================================
+ Hits 21059 21071 +12
- Misses 13005 13019 +14
☔ View full report in Codecov by Sentry. |
ff26adc
to
d85a462
Compare
When merging the `added_path_index` for the different planning request adapters, the `PlanningRequestAdapterChain` was adding them in the wrong order, causing wrong incrementation of the indices. Closes moveit#3463.
d85a462
to
3cec193
Compare
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.
Thanks for finding this bug and providing a fix!
cherry-pick of moveit/moveit#3464
cherry-pick of moveit/moveit#3464
* Port unit test cherry-pick of moveit/moveit#3464 * Increment added_path_index in callAdapter Doesn't work because previous=0 for all recursively called functions. * Pass individual add_path_index vectors to callAdapter --------- Co-authored-by: Hugal31 <hla@lescompanions.com>
* Port unit test cherry-pick of moveit/moveit#3464 * Increment added_path_index in callAdapter Doesn't work because previous=0 for all recursively called functions. * Pass individual add_path_index vectors to callAdapter --------- Co-authored-by: Hugal31 <hla@lescompanions.com>
Description
When merging the
added_path_index
for the different planning request adapters, thePlanningRequestAdapterChain
was adding them in the wrong order, causing wrong incrementation of the indices.Closes #3463.
Checklist