Skip to content
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

separate read + connect + request timeouts #1523

Merged
merged 8 commits into from
Jan 31, 2017
Merged

separate read + connect + request timeouts #1523

merged 8 commits into from
Jan 31, 2017

Conversation

thehesiod
Copy link
Contributor

@thehesiod thehesiod commented Jan 3, 2017

This is an attempt at fixing the timeout issues raised in #1524 + #1180

@codecov-io
Copy link

codecov-io commented Jan 3, 2017

Codecov Report

Merging #1523 into master will increase coverage by <.01%.

@@            Coverage Diff             @@
##           master    #1523      +/-   ##
==========================================
+ Coverage   98.59%   98.59%   +<.01%     
==========================================
  Files          30       30              
  Lines        7055     7071      +16     
  Branches     1176     1179       +3     
==========================================
+ Hits         6956     6972      +16     
  Misses         58       58              
  Partials       41       41
Impacted Files Coverage Δ
aiohttp/client.py 100% <100%> (ø)
aiohttp/connector.py 97.87% <100%> (+0.01%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1811685...94af4b5. Read the comment docs.

- remove unused property set
- add test where TCPConnector does not have a conn_timeout
@thehesiod
Copy link
Contributor Author

I updated the implementation to allow for unlimited timeouts by passingrequest(timeout=None)

@adamrothman
Copy link

@jettify @asvetlov what do you guys think about this? Would make it a lot easier to use aiohttp in more places.

@thehesiod
Copy link
Contributor Author

adding @fafhrd91

@fafhrd91
Copy link
Member

looks good. i am not sure about proper api though. lets add read_timeout but lets wait with documentation.

i did some work on TimeService but for server, we may introduce time_service for client as well, so it'd be possible to use third-party time service.

@thehesiod
Copy link
Contributor Author

thehesiod commented Jan 31, 2017

I think it was a mistake making the default _request timeout 5min, it should have been None and the details handled internally, it makes backwards compatible fixes difficult as we can't differential between the user setting it to 5minutes, or them wanting the default behavior.

@thehesiod
Copy link
Contributor Author

cool, let me know what you want me do.

@fafhrd91
Copy link
Member

request timeout 5min where is it? if we have 5min timeout, it should painless to replace it with None i doubt anyone notice.

@fafhrd91
Copy link
Member

i'll merge this change. if you'd like you can look into time_service integration

@fafhrd91
Copy link
Member

thanks

@fafhrd91 fafhrd91 merged commit 55b1f0e into aio-libs:master Jan 31, 2017
@thehesiod
Copy link
Contributor Author

https://github.com/KeepSafe/aiohttp/pull/1523/files#diff-7dd84b5ef8d5eea2de1dfc5329411dfcL127 let me know if you want me change it to None and update the logic

@fafhrd91
Copy link
Member

ok, lets replace it with None

@thehesiod thehesiod deleted the fix-timeouts branch January 31, 2017 21:21
@lock
Copy link

lock bot commented Oct 29, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants