MozillaSecurity / MozillaSecurity/bugmon
Add whiteboard command for requesting a pernosco trace on a newer build
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 2
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 1
Description
Currently, when the pernosco-wanted keyword is added, Bugmon will attempt to record the trace on the original revision from comment 0. For bugs that sit for a long period, we should add a pernosco_rev command so that you can specify something like pernosco_rev=tip.
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 names no files or tests; start by locating the handling for the pernosco-wanted keyword and the command parsing path. Trace how the original revision is selected, then verify that pernosco_rev=tip requests the trace from the newer build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100