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

Refactor to not use default http client (without timeout) #47

Merged
merged 2 commits into from
Jan 12, 2021

Conversation

thomaspoignant
Copy link
Owner

Description

Not using the default HTTP Client to have the ability to have a timeout.
It is now possible to configure a timeout for HTTP based retriever (HTTP and Github).

Changes include

  • Bugfix (non-breaking change that solves an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking changes (a change that is not backward-compatible and/or changes current functionality)

Closes issue(s)

Resolve #45

Checklist

  • I have tested this code
  • I have added unit test to cover this code
  • I have updated the Readme
  • I have followed the contributing guide

@thomaspoignant thomaspoignant self-assigned this Jan 12, 2021
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@thomaspoignant thomaspoignant merged commit 932e536 into main Jan 12, 2021
@thomaspoignant thomaspoignant deleted the change/45-not-using-default-http branch January 12, 2021 15:46
thomaspoignant added a commit that referenced this pull request Oct 11, 2021
* Refactor to not use default http client (without timeout)
* Add documentation on the README.md
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.

(change) Don't use default http client
1 participant