MozillaSecurity / MozillaSecurity/bugmon
Don't update bug if it's changed since fetching
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 2
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 1
Description
In some situations, bugmon can start working on a bug when it is open but complete after it has been closed. We should handle these mismatches in state by fetching the bug again before reporting and if anything has change in the bug state, drop the changes.
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, tests, or entry points. Trace bugmon's flow from fetching a Bugzilla bug through reporting, then verify the mismatch described in issue #64. Done means a refreshed bug state is checked before reporting and changes are dropped when the state has changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100