mozilla / mozilla/probe-scraper
probe-scraper created one bug for an expiring probe a day earlier than the other ones
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 73
- Avg merge
- 10h
- Merged PRs (30d)
- 3
Description
From https://bugzilla.mozilla.org/show_bug.cgi?id=1735512#c3 :
bugs are only created on "wednesday" runs (which don't happen until UTC thursday) https://github.com/mozilla/probe-scraper/blob/main/probe_scraper/probe_expiry_alert.py#L397-L398
# Only send create bugs on Wednesdays, run the rest for debugging/error detection
dryrun = dryrun or current_date.weekday() != 2
This week bug 1781578 got created on Wednesday UTC while the other bugs got created on Thursday, which is at least odd.
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 in probe_scraper/probe_expiry_alert.py around lines 397-398, where the Wednesday-only bug creation behavior is selected. Compare the UTC dates used by the Wednesday and Thursday runs with the Bugzilla activity linked in the issue. Done means the one-day discrepancy is explained and the expiry alert behavior is corrected or documented with supporting test or run evidence.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100