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

Cherry-Pick #1033: Fix #868 #1057

Merged
merged 6 commits into from
Sep 11, 2018

Conversation

rhaschke
Copy link
Contributor

Cherry-Picking #1033 into Kinetic, with appropriate adaptions to handle old tf.

@rhaschke rhaschke requested a review from v4hn September 10, 2018 06:04
Copy link
Member

@davetcoleman davetcoleman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this!

@davetcoleman davetcoleman merged commit b02ef29 into moveit:kinetic-devel Sep 11, 2018
@rhaschke rhaschke deleted the kinetic-fix-868 branch October 5, 2018 07:58
pull bot pushed a commit to shadow-robot/moveit that referenced this pull request Sep 3, 2020
* Revert "disable waitForCurrentRobotState() for PlanService capability (moveit#923)"

This reverts commit cf2217c.

* only waitForCurrentRobotState when start_state.is_diff

as discussed in moveit#868 (comment)

* reduce code duplication

* use own EventQueue in PlanningSceneMonitor

... to become independent of any capabilities that might block the global queue

* PlanningSceneMonitor: accept parent NodeHandle

* add MIGRATION note
sjahr pushed a commit to sjahr/moveit that referenced this pull request Jun 21, 2024
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

Successfully merging this pull request may close these issues.

2 participants