Cross reference branches with Experimenter API

Open
#2,512 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, backend, data

Research direction

Start by locating the enrollment telemetry handling and the Experimenter API response processing for each experiment. Compare the branch sets from both sources and exclude branches absent from the API response; done when changed or deleted branches no longer appear in results.

Written by the indexing model from the issue text.

Description

We've had instances where a changed/deleted branch has some data in it (likely from QA or other testing before launch) and this leads to an errant branch in the results, which is at best annoying and at worst can break the UI*. We should see if we can cross-reference the branches in enrollment telemetry with the ones in the Experimenter API response for each experiment.

*separately we'll try to make the UI more robust to these issues, but then that leaves us with the best-case scenario where it's still annoying to see errant data in the results

┆Issue is synchronized with this Jira Task

Dominant language
Python
Stars
26
Forks
14
Avg merge
19h 55m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

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/jetstream

All issues in mozilla/jetstream

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.