MozillaSecurity / MozillaSecurity/FuzzManager
[CrashManager] Implement report for new crashes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
This issue is about implementing new crashes reports per day. There should be a configuration option for this in the "User Settings" page and the report should only happen for the tool filter selected there.
The report should be generated every 24 hours in a cron job and it should not include sensitive information.
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 the CrashManager implementation and the User Settings page, then trace how tool filters and scheduled jobs are handled. Clarify the report contents, sensitive-information exclusions, configuration behavior, and delivery before implementation; done means a configurable per-tool daily crash report runs every 24 hours without exposing sensitive data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100