MozillaSecurity / MozillaSecurity/FuzzManager
Stop signature matching for fixed buckets.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
When a bucket is linked to a bug and that bug is fixed, after a grace period (CLEANUP_FIXED_BUCKETS_AFTER_DAYS), we delete that bucket and all contained crashes. This creates a window of time where the bucket still exists (in case we need info for the bug, or the fix is incomplete).
We should have a way to stop using a bucket for incoming crashes without deleting it. This would allow us to see new crashes having the same symptoms after the fix apparently landed. We should account for currently running pools which may continue to report from revisions without the fix. (ie. use a "fixed-by" revision or build id and only disable matching for reports from newer builds).
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 tracing bucket cleanup after CLEANUP_FIXED_BUCKETS_AFTER_DAYS and the incoming-crash signature-matching path. Define how a fixed-by revision or build id affects reports from older versus newer builds; done means the bucket remains available for investigation while newer matching crashes no longer use it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100