prometheus / prometheus/prometheus
Fuzz test Prometheus APIs
Open
Nobody has claimed this yet.
help wanted
kind/enhancement
priority/P3
- Dominant language
- Go
- Stars
- 66.1k
- Forks
- 10.8k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 131
Description
Just found this new tool for Go: https://github.com/dvyukov/go-fuzz
Given that it found quite a few bugs in the standard library, we will certainly find some stuff in Prometheus. Especially as we are now using two text/template style parsers ourselves that might suffer from very similar bugs as the ones found in the stdlib.
Contributor guide
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 names go-fuzz, Prometheus APIs, and two text/template-style parsers, but no source files or tests. Start by reviewing go-fuzz and locating the API and parser entry points; done means agreeing on fuzz targets, adding coverage for them, and showing that the fuzz tests run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100