MozillaSecurity / MozillaSecurity/FuzzManager
Add a flag to opt-in to Bucket cleanup.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
We have Buckets that are very easy to reproduce, that constantly collect crashes that aren't useful after the report has been filed. These buckets grow unbounded because bucketed crashes are not automatically cleaned up.
We should add flag to allow bucket creators to opt-in to the normal periodic crash cleanup threshold. (delete crashes older than x days).
As a safety mechanism, we could add a minimum fill threshold as well (don't cleanup if less than x crashes) so that the bucket is never completely emptied by this cleanup process, if the crash is fixed or stops matching the signature.
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 bucket creation and the existing periodic crash cleanup threshold in FuzzManager. Determine how an opt-in cleanup flag and minimum-fill safeguard would be represented and applied; done means opted-in buckets remove crashes older than the configured threshold without falling below the configured minimum.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100