Details
-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Obsolete
-
Affects Version/s: 0.1.9
-
Fix Version/s: Near Future
-
Component/s: OIOIOI
-
Labels:None
Description
In the future we may need to decouple generating UserResultFor* from the judging of submissions. For example if we support a program-agains-program competitions, then there will be no complete judging of a single submission concept. We will have to run the matches, generate SubmissionResults, and then regenerate all UserResultFor* in batch.
Also, even now if we move a task between rounds, UserResultFor* are not properly updated.
As regenerating this may last long, this should be delegated to a Celery worker.
Also, even now if we move a task between rounds, UserResultFor* are not properly updated.
As regenerating this may last long, this should be delegated to a Celery worker.
Activity
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
169d 19h 10m | 1 | Szymon Acedański | 2013-10-5 18:18 | |||||
|
2395d 22h 10m | 1 | Szymon Acedański | 2020-04-27 16:29 |