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
motion planning stuck after several calls. #2666
Comments
Thanks for reporting an issue. Because we're a volunteer community, providing a pull request with suggested changes is always welcomed. |
to reproduce: #2596 (comment) |
I'm testing what you posted in the PR and can indeed reproduce a dead lock. Now I attached gdb to the thread # 6 processes an new point cloud and wants a write lock on the octomap
and thread # 14 is planning the path your python script requested
I do not understand yet why they are both waiting and why there is a dead lock unfortunately. |
Hi, we are seeing a similar bug in moveit2. Was #2683 copied to moveit2 or is not needed there? |
Description
Overview of your issue here.
Your environment
Steps to reproduce
Expected behaviour
Go to the target joint position
Actual behaviour
Code stuck at
self.hand_commander.go(wait=True)
Backtrace or Console output
No error msg
My guess is this behaviour is related to #2663 which introduce a feature thatThe joint states of
passivejoints must be published in ROS and the CurrentStateMonitor will now wait for them as well.
If so, please provide a possible fix for a robot such as shadow hand.The text was updated successfully, but these errors were encountered: