mozilla / mozilla/probe-scraper
Expiry email resent for previously expiring metrics even if that bug was already closed
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 73
- Avg merge
- 10h
- Merged PRs (30d)
- 3
Description
e.g. we sent emails for browser.searchinit.engine_invalid_webextension with https://bugzilla.mozilla.org/show_bug.cgi?id=1994584 on 2025-10-16 and 2025-10-23
The bug was tackled and closed on 2025-10-18. We still resent the email later.
I think we're missing a check for a bug's status.
We gather a list of bugs here: https://github.com/mozilla/probe-scraper/blob/07baa08949e49210f0aa65ae717765d63b1552ad/probe_scraper/fog_checks.py#L284
But we never check if that bug is already closed. If it is we should remove it from the list.
Contributor guide
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 at probe_scraper/fog_checks.py around line 284, where the list of bugs is gathered, and inspect how Bugzilla data is handled. Verify the example closed bug is excluded from the list so its expiry email is not sent again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100