Transcoder activation not consistent due to round lock period
Open
Nobody has claimed this yet.
bug
- Dominant language
- Shell
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Currently we call "activeTranscoder" when bringing up a new transcoder. But this action could fail if the current round is in a "locked" state (the last 10% of blocks within a round). If this happens, we need to wait and call activate again at the next round.
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
Locate the code that calls activeTranscoder when bringing up a new transcoder, then inspect how the current round and its locked final 10% are detected. Reproduce or test activation during the locked period; done means activation is retried in the next round when the initial call fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100