Revision history [back]

I have gotten this message regularly when running in VirtualBox on one particular machine I use.

I regularly use VMs on different platforms and I'd never run into this issue before.

This BASHonWindows issue helped me realize 1) that I wasn't alone 2) there's a PR.

The root of the matter was that ROS:

assumes that the connect method of non-blocking scoket should return -1 and last_socket_error() should return ROS_SOCKETS_ASYNCHRONOUS_CONNECT_RETURN(=EINPROGRESS). But a non-blocking connect can return 0 when TCP connection to 127.0.0.1 (localhost).