Transcoder error feedback

Open
#39 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
audio-video-rtc

Research direction

Start by tracing the transcoder-to-broadcaster message flow and inspecting the existing TranscodeResponse message. Decide whether a new message type or an extension is appropriate, then define the failure feedback needed when a segment cannot be processed and verify that broadcasters receive it.

Written by the indexing model from the issue text.

Description

Would be good for broadcasters to get some feedback from the transcoder in case a segment couldn't be processed for whatever reason. We can implement a new message type for this, or extend the current TranscodeResponse message to indicate error.

Dominant language
Go
Stars
18
Forks
6
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/go-livepeer-basicnet

All issues in livepeer/go-livepeer-basicnet

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.