Add cleanup for waiting tasks and reject adding more tasks
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
What's the problem? (required)
When there is an issue with Catalyst getting back to update the task status, the task is forever in the waiting phase, which in turn causes the rate limited error for the users.
What's the current behavior? (required)
There is no timeout/cleanup in Livepeer Studio. The only timeout is in Catalyst.
Also, I think that Livepeer Studio should reject and not add to DB any additional tasks if there are already too many of them. Currently, new tasks are added to DB even if rate limited is returned.
Describe a possible solution you've considered (optional)
Add a timeout to the task's lifecycle.
Additional context (optional)
Related Discord thread with the issue which caused record-tester to stop working
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 by tracing the task lifecycle around the waiting phase and the path that persists new tasks when rate limited is returned; the issue names no files or tests. Done means waiting tasks are cleaned up after a timeout and additional tasks are rejected before database insertion when the limit is reached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100