Protocol aware toxics
Open
Nobody has claimed this yet.
ideas
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
We could build protocol aware toxics, e.g.
- HTTP. Send extremely large headers, slow headers, slow body but fast headers, 5xx, infinite redirects..
- Redis. Slow writes and fast reads, out of memory conditions (reads but no writes), ..
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
The issue proposes protocol-aware toxics for HTTP and Redis, including slow or malformed traffic and resource conditions. Begin by determining the project entry points for existing toxics and how protocol-specific behavior would be scoped; done would require an agreed design and implementation covering the selected protocol cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100