feat(client): set a default receive_timeout of 30s#8
Merged
Conversation
sgerrand
added
documentation
Without a timeout the client could hang indefinitely on network issues or a slow Plain API. 30s is overridable via extra_req_opts / ExPlain.new options forwarded to Req.
sgerrand
force-pushed
the
feat/client-default-timeout
branch
from
April 20, 2026 11:50
d5c296b to
b92b82a
Compare
Coverage Report for CI Build 24664886769Coverage remained the same at 100.0%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
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
2 participants
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.
💁 These changes:
receive_timeout: 30_000default toClient.new/3receive_timeout:in the options toExPlain.new/1ExPlain.new/1docs to mention the default