(Catalyst) Handle all support matrix related errors in humanization

Open
#108 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
go
Domain
backend

Research direction

Start at task/runner.go around line 509 and review issue #105 to understand the planned Catalyst error changes. Trace how support-matrix failures reach humanization and identify the full set of errors that must be handled. Done means every Catalyst support-matrix error produces the intended humanized error rather than an unhandled or misleading result.

Written by the indexing model from the issue text.

Description

If Catalyst cannot handle a file because it is not in its support matrix, task-runner should return an error when humanizing that reflects that. The current string matching approach covers a few common support matrix errors from the internals of Catalyst, but once we address https://github.com/livepeer/task-runner/issues/105 we should make sure all support matrix errors are handled.

Dominant language
Go
Stars
3
Forks
1
No merged PRs in 30d

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 livepeer/task-runner

All issues in livepeer/task-runner

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.