Improve metrics_gather.sh parsing process
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by inspecting metrics_gather.sh and tracing how metric output is collected and parsed. Review how optional metrics such as VMAF and malformed output are currently handled. Done should include fault-tolerant parsing, useful errors when metrics cannot be parsed, and a documented decision on whether the metrics return format needs revision.
Written by the indexing model from the issue text.
Description
- make it fault-tolerant, at least for optional metrics like VMAF
- display proper error messages when a metric cannot be parsed
- possibly review the format used to collect metrics
<TD-Linux> the problem is that all the metric parsing is really simple
<TD-Linux> it expects toe return to basically have one metric per line
<TD-Linux> but if the parsing breaks it could add things like extra lines or other junk instead which would mess it up
<TD-Linux> a more rigid metrics_gather.sh, or a better format for returning the metrics datat would help a lot here
- Dominant language
- Python
- Stars
- 21
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 xiph/rd_tool
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Kil Jobs gracefullyOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#14043 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
githubnext/gh-aw-workshop#4455 ·
Maintainers usually reply within 1 day
-
Triage 🩺
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
[BUG] Container scenario crashes without expected_recovery_time, kube DNS example uses retry_waitOpenneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
krkn-chaos/krkn#1627 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#136483 ·
Maintainers usually reply within 1 day