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
roscpp: TransportTCP: Allow socket() to return 0 #1707
Conversation
In situations that an application has stdin closed, socket() may (and will) return 0. This is totally fine.
I would really appreciate if this was also backported to Kinetic.... I will gladly open a PR for the corresponding branch if that's the case. Thank you. |
Just to backup the argument up: The same issue can be found in |
Please update the PR to do so. |
Done |
I am facing the same problem, any updates? |
@ros-pull-request-builder retest this please |
Thanks for the patch. |
* roscpp: TransportTCP: Allow socket() to return 0 In situations that an application has stdin closed, socket() may (and will) return 0. This is totally fine. * TransportUDP: fix incoming socket creation
* roscpp: TransportTCP: Allow socket() to return 0 In situations that an application has stdin closed, socket() may (and will) return 0. This is totally fine. * TransportUDP: fix incoming socket creation
* roscpp: TransportTCP: Allow socket() to return 0 In situations that an application has stdin closed, socket() may (and will) return 0. This is totally fine. * TransportUDP: fix incoming socket creation
In situations that an application has stdin closed, socket() may (and will) return 0. This is totally fine.