mozilla / mozilla/probe-scraper
probe-scraper files duplicate bug for same metrics after version bump
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 73
- Avg merge
- 10h
- Merged PRs (30d)
- 3
Description
probe-scraper filed two bugs for the same expiring metric, likely because the logic did not account for the expiry to be reported a version earlier (#1056).
Example:
- https://bugzilla.mozilla.org/show_bug.cgi?id=2068817 "Remove or update metrics expiring at the end of Firefox 157: extensions.data.storage_local_corrupted_reset" (manually renamed to 158 as workaround to https://github.com/mozilla/probe-scraper/issues/1074 )
- https://bugzilla.mozilla.org/show_bug.cgi?id=2072817 "Remove or update metrics expiring at the end of Firefox 158: extensions.data.storage_local_corrupted_reset"
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 by comparing the two linked Bugzilla reports and reviewing issues #1056 and #1074 for the version-bump and expiry handling context. Trace the probe-scraper logic that creates reports for expiring metrics; done means a metric expiring across a Firefox version bump produces one report rather than duplicates.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100