-
Notifications
You must be signed in to change notification settings - Fork 131
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
rqt_graph prints KeyError 'bb' #321
Comments
Same happened to me and some other users. I needed to kill everything that was running and launch everything again to make rqt_graph work. |
A SSCCE (Short, Self Contained, Correct (Compilable), Example) would really help to find the actual problem. Please consider providing step-by-step instructions how to reproduce this. |
Agreed but I haven't been able to get it to happen consistently. |
Ok, I just got it to reproduce in one easy way. Shell 1:
Shell 2:
Now do Control+Z (send to background) to this shell. Then we can execute:
And it will crash with that problem. I suspect it has something to do with the node not being able to answer ( |
@awesomebytes I can reproduce your use case. But I think your expectations are wrong. Ctrl-Z does not send the process to background - it suspends the process. And therefore it can not respond to any requests anymore. If you run @ablasdel I assume you are having a similar situation where one of the nodes is not responding. But in your case it might be a node doing some long-running operation and is therefore not able to respond. |
@dirk-thomas That makes sense I will look into trying to reproduce that knowing that. Either way rqt dotgraph should probably handle it more gracefully than a trace if it can't communicate with a node right? |
The better handling has been added in ros-visualization/qt_gui_core@97985bd But it would be good to fix |
If you uncheck the |
I don't think |
awesome thanks dirk! |
This seems to be the same thing experienced in this ros answers question: http://answers.ros.org/question/192782/rqt_graph-crashes/
Unfortunately re-installing rqt_graph doesn't seem to fix it for us after installing 0.3.11.
rqt-graph & rqt-common-plugins
content of the rqt_gui.ini file of the computer in question
The text was updated successfully, but these errors were encountered: