You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature or improvement you're requesting
Want a logic to retry API if sock_read on stream is not working in <2 seconds. Sometimes this happens on a web-server due to various issues with the requesting library (requests.request / aiohttp). Currently only
is supported. Perhaps accepting additional lengths on request_timeout, or adding a new kwarg for timeout object, or accepting a dictionary instead a tuple on request_timeout would be helpful.
Additional context
No response
The text was updated successfully, but these errors were encountered:
suhjohn
changed the title
ClientTimeout object support - sock_read, sock_connect
ClientTimeout support on all API calls - sock_read, sock_connect
Mar 23, 2023
suhjohn
changed the title
ClientTimeout support on all API calls - sock_read, sock_connect
Additional ClientTimeout parameter support on async API calls - sock_read, sock_connect
Mar 23, 2023
Describe the feature or improvement you're requesting
Want a logic to retry API if sock_read on stream is not working in <2 seconds. Sometimes this happens on a web-server due to various issues with the requesting library (requests.request / aiohttp). Currently only
is supported. Perhaps accepting additional lengths on request_timeout, or adding a new kwarg for timeout object, or accepting a dictionary instead a tuple on request_timeout would be helpful.
Additional context
No response
The text was updated successfully, but these errors were encountered: