failed submissions count #96

New Issue

manuel · 2025-12-06T08:49:00+08:00

manuel commented

2025-12-06 08:49:00 +08:00

some students don't test compilation or run their code locally before submitting. we should be able to block them easily. block can be by group or stage. the most common usage would be to prevent students who failed compilation to resubmit for a few hours/rest of the day.

detect failed stage/group
block user or whole repo for x hours, similar to submission count

some students don't test compilation or run their code locally before submitting. we should be able to block them easily. block can be by group or stage. the most common usage would be to prevent students who failed compilation to resubmit for a few hours/rest of the day. - [ ] detect failed stage/group - [ ] block user or whole repo for `x` hours, similar to submission count

manuel added the

enhancement

label 2025-12-06 08:49:00 +08:00

张泊明518370910136 was assigned by manuel

2025-12-06 08:49:01 +08:00

张泊明518370910136 commented

2025-12-07 17:15:14 +08:00

Any idea about the format of the config?

manuel commented

2025-12-10 07:53:33 +08:00

either similar to group limitation unless this is easier/better to have a config at a stage level?

eg. max 1 failed compilation in 2h, if 2 failed then blocked for 2h

either similar to group limitation unless this is easier/better to have a config at a stage level? eg. max 1 failed compilation in 2h, if 2 failed then blocked for 2h

张泊明518370910136 commented

2026-03-26 14:39:08 +08:00

So we only need to consider blocking submission failed on compilation stage? I do not think block by failed group is a good idea as the compilation stage may not have a group, or TAs need to add it.

manuel commented

2026-03-26 15:34:47 +08:00

we usually have a group build for compilation. students might push docs, or partial work so build is not enabled by default (at least in my courses, but that should be easy to extend to others)

having by group could allow us to block students who "crash" on the OJ part more than 3 times a day for instance

by default the only thing that we always run is HC. all the rest build/cq/oj are optional (we use the cover dependency to run build with oj specified)

we usually have a group `build` for compilation. students might push docs, or partial work so build is not enabled by default (at least in my courses, but that should be easy to extend to others) having by group could allow us to block students who "crash" on the OJ part more than 3 times a day for instance by default the only thing that we always run is HC. all the rest build/cq/oj are optional (we use the cover dependency to run build with oj specified)

VAHE MELKONYAN525370990019 added a new dependency 2026-05-15 13:30:52 +08:00

vahem27/Personal#1 - Add some UI.

VAHE MELKONYAN525370990019 removed a dependency 2026-05-15 13:30:57 +08:00

vahem27/Personal#1 - Add some UI.

Sign in to join this conversation.