Skip to content
This repository has been archived by the owner on Jul 12, 2024. It is now read-only.

[roswtf] WARNING Communication with node [/rosout] is very slow #6

Closed
kejxu opened this issue Oct 10, 2018 · 5 comments · Fixed by ros/ros_comm#1872
Closed

[roswtf] WARNING Communication with node [/rosout] is very slow #6

kejxu opened this issue Oct 10, 2018 · 5 comments · Fixed by ros/ros_comm#1872
Assignees
Labels
bug Something isn't working wait-for-upstream This is in the upstream pipeline.

Comments

@kejxu
Copy link
Contributor

kejxu commented Oct 10, 2018

C:\temp\test_ws\src\my_tut>roswtf
Loaded plugin tf.tfwtf
Package: my_tut
================================================================================
Static checks summary:
Found 1 error(s).
�[31m�[1mERROR�[0m Local network configuration is invalid: Local hostname [DESKTOP-E0BPROA] resolves to [2001:4898:d8:27:d993:bad8:bf0d:182f,fe80::5464:3b68:972d:8714%7,2001:4898:d8:27:5464:3b68:972d:8714], which does not appear to be a local IP address ['10.131.8.171'].
================================================================================
Beginning tests of your ROS graph. These may take awhile...
analyzing graph...
... done analyzing graph
running graph rules...
ERROR: connection refused to [http://DESKTOP-E0BPROA:60645/]
... done running graph rules
Online checks summary:
Found 2 warning(s).
Warnings are things that may be just fine, but are sometimes at fault
�[1mWARNING�[0m Communication with node [/rosout] is very slow
�[1mWARNING�[0m The following nodes are unexpectedly connected:
 * /rosout->/rqt_gui_py_node_8208 (/rosout_agg)
@ooeygui ooeygui added bug Something isn't working help wanted Extra attention is needed labels Oct 23, 2018
@ooeygui ooeygui assigned ooeygui and unassigned kejxu May 17, 2019
@ooeygui
Copy link
Member

ooeygui commented May 17, 2019

This is related to localhost

@seanyen
Copy link
Contributor

seanyen commented Jun 7, 2019

It could be related to: ms-iot/ros_comm#56

@imcnanie
Copy link

imcnanie commented Sep 4, 2019

Any updates on this?

@ooeygui
Copy link
Member

ooeygui commented Sep 19, 2019

@imcnanie We changed the setup script to use 127.0.01 which prevented a DNS lookup on each connection.

@seanyen seanyen added wait-for-upstream This is in the upstream pipeline. and removed help wanted Extra attention is needed labels Feb 4, 2020
@seanyen
Copy link
Contributor

seanyen commented Feb 24, 2020

I am closing it now since the fix is merged by the upstream.

@seanyen seanyen closed this as completed Feb 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working wait-for-upstream This is in the upstream pipeline.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants