We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This seems to just be a quirk in Jython's socket implementation (see jython issue 1806):
>>> import socket >>> s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) >>> s.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) >>> s.bind(("localhost", 0)) >>> s.settimeout(0.5) >>> s.getsockname() ('127.0.0.1', 0)
But, if we add a call to s.listen, the next s.getsockname() returns the correct info:
s.listen
s.getsockname()
>>> s.listen(1) >>> s.getsockname() ('127.0.0.1', 57581)
I'm not sure how much you care about Jython suport, but it seems like it would pretty safe to update self.port in Server.start after calling listen.
self.port
Server.start
listen
The text was updated successfully, but these errors were encountered:
a8214fd
Thanks! Fix implemented as understood from your description (better late than never). Give me a shout if the problem is not solved.
Best, Thomas
Sorry, something went wrong.
Release rpyc 3.4.3
0cc824d
- Add missing endpoints config in ThreadPoolServer (#222) - Fix jython support (#156,#171) - Improve documentation (#158,#185,#189,#198 and more)
No branches or pull requests
This seems to just be a quirk in Jython's socket implementation (see jython issue 1806):
But, if we add a call to
s.listen
, the nexts.getsockname()
returns the correct info:I'm not sure how much you care about Jython suport, but it seems like it would pretty safe to update
self.port
inServer.start
after callinglisten
.The text was updated successfully, but these errors were encountered: