-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Add timeout to requests calls #3752
base: main
Are you sure you want to change the base?
Conversation
FYI - This change was autogenerated from a GitHub app - called Pixeebot. A code-quality GitHub App; like Dependabot, but for source code. Feel free to check it our for more details for how you can install it onto your project's repo for continued code hardening and code security recommendations. |
❌ pre-commit failed. |
Co-authored-by: pixeebot[bot] <104101892+pixeebot[bot]@users.noreply.github.com>
❌ pre-commit failed. |
Co-authored-by: pixeebot[bot] <104101892+pixeebot[bot]@users.noreply.github.com>
❌ pre-commit failed. |
Any chance you've had the time to review these changes? If you're not interested implementing them at this time, no worries. I can close the PR and follow up with additional changes in the future. Also, this plugin is free for non-commercial open sourced projects, so feel free to give it an install if you want to see the other recommended PRs. (GitHub Apps - pixeebot) Thanks, |
Many developers will be surprised to learn that
requests
library calls do not include timeouts by default. This means that an attempted request could hang indefinitely if no connection is established or if no data is received from the server.The requests documentation suggests that most calls should explicitly include a
timeout
parameter. This codemod adds a default timeout value in order to set an upper bound on connection times and ensure that requests connect or fail in a timely manner. This value also ensures the connection will timeout if the server does not respond with data within a reasonable amount of time.While timeout values will be application dependent, we believe that this codemod adds a reasonable default that serves as an appropriate ceiling for most situations.
Our changes look like the following:
More reading
Powered by: pixeebot (codemod ID: pixee:python/add-requests-timeouts)