fix(honcho): make client timeout configurable#10372
Closed
rahimsais wants to merge 1 commit into
Closed
Conversation
4 tasks
Contributor
|
Thanks for the contribution, @rahimsais! This is exactly the right fix. Unfortunately, an equivalent implementation landed on
Main's implementation is a superset of what this PR adds, so closing as implemented. Automated hermes-sweeper review. |
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
timeout_secondstoHonchoClientConfigHONCHO_TIMEOUT_SECONDSProblem
The Honcho client timeout is currently fixed in code. That is too rigid for self-hosted or local deployments, and it forces one hardcoded policy instead of letting operators tune the timeout explicitly.
Notes
This is related to #8527 but takes a config-driven approach instead of hardcoding a longer timeout for local base URLs only.
Test Plan