-
Notifications
You must be signed in to change notification settings - Fork 49
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
Default connect timeout doesn't work #50
Comments
There is a bug (no open issue for it, but it's already been fixed in the dev branch) in 1.0.5 where the docs specify the default timeout as 60 seconds but it's actually None (so unlimited). Sorry about that. You can specify a timeout manually though:
|
@cole is it known when next release which includes this fix will be available? |
@decaz not yet. I'd recommend you specify a timeout manually (60 will be the future default). |
The default is now 60 seconds in 1.0.6. |
I have a problem with connect operation not terminating after timeout. For example you can try to connect to wrong port:
This code hangs for a long-long time. I also tried to wrap connect into
asyncio.wait_for
but it also doesn't work.The text was updated successfully, but these errors were encountered: