Bug Report: Submissions stuck at "Submitting" and "Submitted" (Evaluation not starting)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 12/100
Research direction
The payload names no source files, tests or entry points, only a live instance and two submission IDs (475, 464). This is an operator support request, not a code task: the issue asks maintainers to inspect the stuck submissions and reset a user's daily quota. Done would mean the cause of the stalled upload and the evaluation hang is identified and the affected submissions are resolved. Start with the maintainers, not a patch.
Written by the indexing model from the issue text.
Description
Dear Team,
I am encountering two persistent issues with my submissions on a Codabench instance (submit.learn2design2026.com, Competition ID: 4).
Affected Account Username: trigerfly
Issue 1: Frontend Upload Freeze
My recent attempt hangs indefinitely in the "Submitting" status. Because of this issue, the platform automatically deducts these stalled attempts from my daily quota, locking me out at "5 out of 5" without the file ever reaching the evaluation cluster.
Stuck Submission ID: 475
Issue 2: Evaluation Not Starting
I have a previous submission that successfully reached the "Submitted" status, but it never progressed to "Running" or completed the evaluation.
Stuck Submission ID: 464
Both submission archives are standard, valid ZIP files (~1 KB, containing only submission.py and requirements.txt).
Could you please investigate these frozen submissions and kindly reset my daily quota so I can successfully participate today?
Thank you and best regards!
- Dominant language
- Python
- Stars
- 183
- Forks
- 80
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 33
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from codalab/codabench
-
Wrong count for failed submissions in Resource interfacePossibly taken @ihsaan-ullah claimed this 5 days ago. OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Resource Interface: Improve time formatPossibly taken @ihsaan-ullah claimed this 4 days ago. OpenBeginner Enhancement UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Email redesignOpenEnhancement UI
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
Unused datasets cleanup counts solution datasets and deletes their solutionsPossibly taken @ihsaan-ullah claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Discussion
Difficulty 4/5 1-2 days Newbie friendliness 25/100
codalab/codabench#2640 · 2 comments ·
Maintainers usually reply within 1 day
All issues in codalab/codabench
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
tharje/spooler-v2#20 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Bump version of azure-servicebusPossibly taken @joostlek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
home-assistant/core#186275 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 72/100