Support for connection timed out toxic
Open
Nobody has claimed this yet.
question
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice to add a toxic that can simulate a connection timed out. Such feature can be really useful for testing out client connection retry configurations.
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
No files or tests are named in the issue. Start by reviewing the existing toxic implementations and their tests, then determine how a connection-timeout toxic should behave and how clients can verify retry handling; done means the toxic reliably simulates a connection timeout for those tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100