livepeer / livepeer/go-livepeer
Broadcaster should prefer Orchestrators with Capability_WSTransport capability
Open
Nobody has claimed this yet.
area: broadcasting
status: backlog
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
This issue has no description.
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
The issue provides no description, files, tests, or entry points to inspect. Start by locating the Broadcaster logic that selects Orchestrators and the Capability_WSTransport capability definition. Done means the selection behavior prefers eligible Orchestrators with that capability, with appropriate tests documenting the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100