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
Connect your code to JIRA
Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.
Git & Mercurial in the cloud
Collaborate across unlimited private code repositories.
Git behind the firewall
Manage and collaborate on Git repositories behind a firewall.
Browse and search code
Browse, search, and track source code repositories.
