Submissions stuck in "Scoring" when broker error occurs during compute_worker PATCH (non-transactional re-enqueue)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 176
- Forks
- 74
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 21
Description
Problem
When the compute_worker PATCHes a submission with status=Scoring, the site re-enqueues the scoring task before committing the new status and outside any transaction. If the broker publish raises (RabbitMQ unreachable, ConnectionError, channel error, broker restart, …), no message ever reaches the compute-worker queue. The DB row is still moved
to Scoring on the next code path, so the submission stays in Scoring forever — no retry, no failover, no cleanup picks it up.
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
Trace the compute_worker PATCH handling for submissions entering Scoring and the scoring-task re-enqueue path. Reproduce or inspect behavior when broker publishing fails, then determine how status persistence and re-enqueue should be coordinated. Done means a broker error cannot leave a submission permanently stuck in Scoring.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rabbitmq
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100