-
Notifications
You must be signed in to change notification settings - Fork 21
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
[Improve] add adaptive recuring non blocking timeout handling for Scrapper.py get_page method #29
Comments
I am interested to work on this issue. |
@vipuldcoder address the issue that you already have, without setting up the node and knowing the application you won't be able to tackle this one. |
Interested working on this for #ggsoc. Thought of using Python backoff library. It accepts a give up time parameter so that waiting time does not become infitity. |
Great you can start working on it then pull a PR for same. |
…exponential backoff - Exponential backoff algorithm used to handle network issues using 'backoff' library - 'max_time' parameter used to add timeout References 1. https://github.com/litl/backoff 2. https://en.wikipedia.org/wiki/Exponential_backoff Fixes rajatkb#29
…exponential backoff - Exponential backoff algorithm used to handle network issues using 'backoff' library - 'max_time' parameter used to add timeout References 1. https://github.com/litl/backoff 2. https://en.wikipedia.org/wiki/Exponential_backoff Fixes rajatkb#29
…exponential backoff - Exponential backoff algorithm used to handle network issues using 'backoff' library - 'max_time' parameter used to add timeout References 1. https://github.com/litl/backoff 2. https://en.wikipedia.org/wiki/Exponential_backoff Fixes rajatkb#29
Please review #70 |
Requirement
Where to look
Update: An implementation is provided for exponential wait time increase in utility package as AdaptiveRequest class. The issue is not resolved, as in case of fault network the system may end up raising its wait time indefinite, i.e leading back to the old problem of having no wait time for request.
The text was updated successfully, but these errors were encountered: