Define open_timeout and read_timeout independently
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 41
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Hi, is there any reason why we can't define open_timeout and read_timeout independently?
I would be happy to implement it; I think the following code would be enough:
def open_timeout=(new_timeout)
@http.open_timeout = new_timeout
end
def read_timeout=(new_timeout)
@http.read_timeout = new_timeout
end
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing timeout configuration and tests in the repository, using open_timeout and read_timeout as search terms. Check how the HTTP client currently handles these values. Done means each timeout can be set independently without changing the other, with tests covering both setters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100