feat: configure HTTP timeout via env#11
Closed
saurabhhhcodes wants to merge 1 commit into
Closed
Conversation
Author
|
Closing this older version to keep the review queue clean. The current replacement for the configurable timeout work is #25. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
APIDRIFT_HTTP_TIMEOUT_MSparsing with a safe 10s default and validation for positive integer values.env.exampleand READMEFixes #7
Validation
git diff --checknode --check src/utils/httpTimeout.jsnode --check src/core/fetcher.jsnode --check src/discovery/openapi.jsnode --check src/discovery/graphql.jsnpm test -- --runInBandcould not run locally becausenpmis not available in this shellGSSoC labels requested
Please add/keep
gssocand any required difficulty/type scoring labels if this is accepted.