livepeer / livepeer/go-livepeer
Do not save source segments to disk
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
Right now orchestrator always [saves](https://github.com/livepeer/go-livepeer/blob/master/core/orchestrator.go#L280) source segment to disk.
But in case remote transcoders used, this saved files isn't used, and just [deleted](https://github.com/livepeer/go-livepeer/blob/master/core/orchestrator.go#L353) moment after.
Contributor guide
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 in core/orchestrator.go at the source-segment save near line 280 and the deletion near line 353. Trace the remote-transcoder path and verify that source segments are not written to disk when they are immediately discarded, while required local-transcoder behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100