fix: http.timeout
default does not match the documentation
#373
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ran into a fun problem today where while running a test case that was processing 4,000+ schemas my tests began to slow to a crawl. Thinking it was a
fetch
problem I dug into the documentation and noticed that the docs mentionhttp.timeout
having a 5s default.Turns out it's actually 60s! 😰
This drops thehttp.timeout
default down to 5s in order to match the docs.