"Probe Scraper: Error on parsing metric or ping files Inbox" emails could be nicer

Open
#305 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend, content

Research direction

No files, tests, or entry points are named in the issue. Start by locating the code that generates the “Probe Scraper: Error on parsing metric or ping files Inbox” emails and identify how repository SHAs are currently presented. Done means the emails explain their meaning and recommended response, and include repository names alongside SHAs.

Written by the indexing model from the issue text.

Description

The emails we get on the mailing list are informative, but I think they could be better.

I think it'd be really helpful if the emails contained:

  • Front matter to introduce what this email is and what it means. Does this mean schema deploys are blocked until they're fixed? Does this mean everything is gonna be broken until a button is pushed?
  • Repository names so that the SHAs make sense
  • Back matter to explain what should be done about this. Should it be ignored unless it happens again? Should we engage on #glean-dev to find a solution?
Dominant language
Python
Stars
26
Forks
73
Avg merge
10h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/probe-scraper

All issues in mozilla/probe-scraper

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.