Container reset can skip restoring the autograder files without any error
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 63/100
Research direction
Read the container creation and reset paths changed by #375, focusing on where the autograder files are saved and restored. Trace how a failed save is handled and how reset reports success when the saved copy is missing. Done when a failed save causes the container to be discarded or a missing copy makes reset fail, preventing later submissions from reusing modified files.
Written by the indexing model from the issue text.
Description
A container reset can skip restoring the autograder's files without reporting an error.
When an assignment's container is created, #375 saves a copy of the autograder files (/autograder/source). Before each submission, the reset puts that saved copy back, so nothing one student's code changed affects the next student.
If saving that copy fails when the container is created, the code only logs a warning and keeps using the container. After that, every reset skips the restore step and still reports success. Anything a student's code writes into /autograder/source (for example, editing a test file) then stays there for every later submission to that assignment.
Fix: if the copy can't be saved, throw the container away so the next submission creates a fresh one. Or make the reset fail when the saved copy is missing.
- Dominant language
- Python
- Stars
- 13
- Forks
- 0
- Avg merge
- 2h 4m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 kiat/codeAssist
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
kiat/codeAssist#391 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
kiat/codeAssist#364 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
kiat/codeAssist#393 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
kiat/codeAssist#390 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
kiat/codeAssist#389 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
aws-samples/sample-per-model-bedrock#243 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
FuRongJun-1999/dsh-memory#404 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PennyLaneAI/catalyst#3337 ·
Maintainers usually reply within 1 day
-
Workflow.schedule stops when a cron deadline passes before sleepPossibly taken @HuaTNA claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day