queueing and reprocessing failures
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 40
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
A video may fail to sync for many different reasons and may not retry until a new video is published or we have the creator complain to us. We should put all the "legit" failures into a queue and have at least 1 server reprocess those.
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
No files, tests, or entry points are named. Start by tracing how video sync failures are recorded and retried, then identify which failures are safe to reprocess and how a queue worker would run. Done means legitimate failures are queued, reprocessed by at least one server, and no longer depend on a new publication or creator report.
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
- 25/100