cshean
commented
5 years ago This one requires a lot of CSS work from what I can tell. I don't think it's worth attempting at this point.
Open bwornom7 opened 5 years ago
cshean
commented
5 years ago This one requires a lot of CSS work from what I can tell. I don't think it's worth attempting at this point.
Add two new attributes Submission: “submission status” and "checkout".
"Submission status" can have one of two values: “review” or “judged”. "Checkout" has the ID of a judge that is currently reviewing the submission. Add two new columns to the /judge view that display these attribute values. By default, the filter should display only records with the value "review."
When a contestant submits an attempt, if the system determines that the result is correct, TLE, or runtime crash, the status should be set to “judged.”
If the system determines that the result is wrong answer, incomplete output, or extra output, the status should be set to “review,” and the contestant sees “pending” as the result.
When a judge selects a submission from the list, the system records the judge's id in the submission's "checkout" attribute and displays the submission details popup. The judge reviews the submission and modifies the result, if desired, then changes the status to "judged."
When one judge has a submission open to review and another judge attempts to open the same submission, the system should display a dialog to the second judge indicating which judge has the submission open for review and asking if the judge wishes to override.
To handle multiuser conflicts, add a version number attribute to the submission and increment / check it using the techniques discussed in class.