Remove special case discrete metrics transition logic
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
Research direction
Locate the ArgoExecutor implementation and identify the special-case transition logic for non-discrete metrics. Confirm how automated analysis now handles metrics, remove the obsolete transition path, and run the relevant test suite to verify behavior remains correct.
Written by the indexing model from the issue text.
Description
After experiments no longer use non-discrete metrics for automated analysis, we can remove the special-case logic we put into the ArgoExecutor to handle the transition.
Originally posted by @scholtzan in https://github.com/mozilla/jetstream/pull/3067#discussion_r2997733734
┆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
- 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.
More from mozilla/jetstream
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in mozilla/jetstream
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100