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

Add timeout to requests calls #3752

Closed
wants to merge 4 commits into from
Closed

Conversation

pixeeai
Copy link

@pixeeai pixeeai commented May 3, 2024

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:

 import requests
 
- requests.get("http://example.com")
+ requests.get("http://example.com", timeout=60)
More reading

Powered by: pixeebot (codemod ID: pixee:python/add-requests-timeouts)

pixeebot bot and others added 2 commits May 3, 2024 16:23
Co-authored-by: pixeebot[bot] <104101892+pixeebot[bot]@users.noreply.github.com>
@pixeeai
Copy link
Author

pixeeai commented May 3, 2024

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.

Copy link

github-actions bot commented May 3, 2024

pre-commit failed.
Please run pre-commit run --all-files locally and commit the changes.
Find more information in the repository's CONTRIBUTING.md

Co-authored-by: pixeebot[bot] <104101892+pixeebot[bot]@users.noreply.github.com>
Copy link

github-actions bot commented May 3, 2024

pre-commit failed.
Please run pre-commit run --all-files locally and commit the changes.
Find more information in the repository's CONTRIBUTING.md

Co-authored-by: pixeebot[bot] <104101892+pixeebot[bot]@users.noreply.github.com>
Copy link

github-actions bot commented May 7, 2024

pre-commit failed.
Please run pre-commit run --all-files locally and commit the changes.
Find more information in the repository's CONTRIBUTING.md

@pixeeai
Copy link
Author

pixeeai commented Nov 2, 2024

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,
Zach

@pixeeai pixeeai closed this Nov 29, 2024
@x64x2
Copy link

x64x2 commented Dec 1, 2024

Stop Contributing, Project been dead for months now

@bitplane
Copy link
Collaborator

bitplane commented Dec 2, 2024

@pixeeai Please inform your owner that they should not blindly change random functions in machine learning projects. secure random number generators add nothing but overhead, and where the previous generator was used with a known seed, you risk messing up the training and test data splits.

@pixeeai
Copy link
Author

pixeeai commented Dec 2, 2024

Stop Contributing, Project been dead for months now

Apologies, was not aware it was the development has paused.

Thanks,
Zach

@pixeeai
Copy link
Author

pixeeai commented Dec 2, 2024

@pixeeai Please inform your owner that they should not blindly change random functions in machine learning projects. secure random number generators add nothing but overhead, and where the previous generator was used with a known seed, you risk messing up the training and test data splits.

Apologies as well, the intended changes were specifically for adding timeout values to the requests. Did not mean to pull in the other changes regarding the random number generator.

This is what it was intended to be pulled from:
https://github.com/Pixee-Bot-Python/Open-Assistant/pull/5/files

Sorry again!

Take care,
Zach

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants