When submission size exceed free disk space on sandbox don't even send it to the sandbox
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
No file or test is named in the issue. Start by locating the submission packaging and sandbox-dispatch paths, then trace how the 164M submission reaches the sandbox. Done means an oversized submission is warned about and rejected before sandbox transfer, without exhausting sandbox disk space.
Written by the indexing model from the issue text.
Description
e.g. https://tmc.mooc.fi/mooc/submissions/759113#logs contained 164M text file and we run out of space on sandbox.
Really we should have just warned that submission exceeds max submission size.
[3.296072] tar: ./src/sanat.txt: Wrote only 4096 of 10240 bytes
[4.461435] tar: ./src/sanakirja/Main.java: Cannot write: No space left on device
[4.461547] tar: ./src/sanakirja/MuistavaSanakirja.java: Cannot write: No space left on device
[4.461805] tar: ./test/tmp/tmp65111.txt: Cannot write: No space left on device
[4.461988] tar: ./test/MuistavaSanakirjaTest.java: Cannot write: No space left on device
[4.462106] tar: ./test/sanat.txt: Cannot write: No space left on device
[4.469226] tar: Exiting with failure status due to previous errors
[4.469559] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
- Dominant language
- Ruby
- Stars
- 51
- Forks
- 42
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 1
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.
More from testmycode/tmc-server
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
testmycode/tmc-server#590 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
testmycode/tmc-server#576 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
testmycode/tmc-server#488 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
testmycode/tmc-server#487 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
testmycode/tmc-server#477 · 2 comments ·
All issues in testmycode/tmc-server
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
バグ
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voxpupuli/puppet-epel#186 · 1 comment ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) OpenBug Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100