livepeer / livepeer/task-runner
(Catalyst) Handle all support matrix related errors in humanization
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
If Catalyst cannot handle a file because it is not in its support matrix, task-runner should return an [error](https://github.com/livepeer/task-runner/blob/fc8b4f03d4fe323d04465880325c23e0b40e4593/task/runner.go#L509) 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.
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.
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.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100