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
- All
- Comments
- History
- Activity
- Transitions
- Commits
Szymon Acedański
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 1 ] |
Szymon Acedański
made changes -
| Summary | Admin can reattach problem_instance to another round, but UserResultForRound objects aren't updated | Support for re-generating UserResultFor* |
Szymon Acedański
made changes -
| 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. |
Szymon Acedański
made changes -
| Fix Version/s | Near Future [ 11001 ] |
Szymon Acedański
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Assignee | Szymon Acedański [ accek ] | |
| Resolution | Obsolete [ 7 ] |
