failed submissions count #96

Open
opened 2025-12-06 08:49:00 +08:00 by manuel · 2 comments
Owner

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

Any idea about the format of the config?

Any idea about the format of the config?
Author
Owner

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
Sign in to join this conversation.
No description provided.