Users can then click a button to copy the sample input instead of scrolling and dragging (if it's long).

Ability to specify which pool of judges should judge a particular problem, to ensure consistent timings.

Would make it easier for new users to register than having to log into their email and click a link.

May be we should add total points to organization page.

Total problem count is considered but implementation could not be efficient.

Contest rating and/or medals would be a nice incentive for people to actually participate.

Checkbox defaulted to false to avoid spoils; useful for teachers. Checking it should add another column to the table.

That field is ManyToMany, implementation should not cause one query per row. That page is already slow enough as it with only one query for the entire table.

Currently only the main submission view is auto updated. All other ones are not. This change requires the event server to send the problem and user id, in order that the JS can know which submissions to retrieve and add.

A popular browser for Android devices. They look fine as boxes, but consistency is nice.

Closes file handles on error conditions despite being in use.

Traceback (most recent call last):

  File "/code/site/judge/bridge/judgelist.py", line 23, in _handle_free_judge
    judge.submit(id, problem, language, source)

  File "/code/site/judge/bridge/judgehandler.py", line 124, in submit
    'short-circuit': short,

  File "/code/site/event_socket_server/helpers.py", line 35, in send
    self._send(size_pack.pack(len(data)) + data, callback)

  File "/code/site/event_socket_server/handler.py", line 17, in _send
    return self.server.send(self, data, callback)

  File "/code/site/event_socket_server/base_server.py", line 146, in send
    self._send_queue[client.fileno()].append(SendMessage(data, callback))

  File "/code/site/event_socket_server/handler.py", line 11, in fileno
    return self._socket.fileno()

  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)

  File "/usr/lib/python2.7/socket.py", line 170, in _dummy
    raise error(EBADF, 'Bad file descriptor')

error: [Errno 9] Bad file descriptor

Implementation is simply subclassing a different class in admin.py, but it requires Django 1.7 (#30). The base feature is already implemented in #29.

Removing a dead judge should not involve taking down the bridge.

Traceback (most recent call last):

  File "/code/site/judge/bridge/judgehandler.py", line 165, in packet
    handler(data)

  File "/code/site/judge/bridge/judgecallback.py", line 85, in on_grading_end
    super(DjangoJudgeHandler, self).on_grading_end(packet)

  File "/code/site/judge/bridge/judgehandler.py", line 187, in on_grading_end
    self._free_self(packet)

  File "/code/site/judge/bridge/judgehandler.py", line 237, in _free_self
    self.server.judges.on_judge_free(self, packet['submission-id'])

  File "/code/site/judge/bridge/judgelist.py", line 57, in on_judge_free
    self._handle_free_judge(judge)

  File "/code/site/judge/bridge/judgelist.py", line 26, in _handle_free_judge
    self.judges.remove(judge)

KeyError: <judge.bridge.judgecallback.DjangoJudgeHandler object at 0x22a9e10>

Select2 widgets in the admin have the wrong width (compared to other widgets) and it is impossible to operate at the default width.

We have been stuck on django 1.6 for far too long, mainly because openshift doesn't support python 2.7, prerequisite for django 1.7. But now we are no longer tied to openshift, we should try to upgrade to 1.7. At the very least, #29 can be completed.

For wherever we need to link licenses, it would be good to have them on-site along with a link off-site to their official pages.

References #43

Useful for navigating backwards in browser.

Currently, even after the judge acknowledges the submission and starts handling it, until execution is ready, the submission is always in the QU state, making it hard to know what's actually happening, made worse by slow generators. Proposal is for judgecallback.py to override on_submission_acknowledged and perform required operations.

The current judge contain contains a state called compiled, which is never used and its name is misleading. A code of P is recommended because not all language compiles, and that it is no substring of any other code. Substring is bad because of this optimization:

if submission.status in 'QUGCEIEAB'

Like for problems, but without the Mathjax.

Such that contestants can be notified of upcoming contests.

Much easier to click on where you live than to scroll/search through a combobox. Also gives the site a modern feel, which is important to prospective users.

Unchecking free start to put a free start in the upcoming contests section and checking it before anyone joins when it actually starts is really tedious.

A link to user submissions on http://www.dmoj.ca/submissions/ would be more convenient than navigating to your user page and hitting "View submissions" there

Brought over from Redmine, http://dev.ivybits.tk/issues/161, and requested a long time ago.

Particularly useful when using the sort-by-points feature.

http://sass-lang.com/

Ability to hack incorrect submissions on a contest and on the main judge.

After hacking, admin can choose to manually add hack to main tests. List of hacks page like submissions page would be good.

Why don't we split them up into things like, user, problem, submission, contest, judges, and other smaller files?

http://www.acooke.org/cute/UsingaDire0.html is how we can split up models. Admin should be able to exist anywhere as long as imported.

Currently the DM::OJ banner displayed is text, and though a font is specified the banner looks horrible with some fonts (such as those where the J extends below the O by half its length). An image banner would work, but not handle resizing well.

Maybe a custom font?

Seems like there is an app for it.

http://django-reversion.readthedocs.org/en/latest/

@Xyene will no longer need to be angry over people overwriting his changes.

Though unlikely, it is possible that we may at any time lose portions of our database to unforeseen bugs. Or that we may be asked by regional contest organizers to remove their problems from the DMOJ if/when they develop their own OJ (funding et al.)

When this happens, it would be highly inconvenient to those who have submitted those problems to have to visit each problem and save their source. In general, a backup feature located on the users page would be useful in the long run.

It would operate with two options: Backup all and Backup best. Based on the option, a zip/tar file would be generated and the user would be able to download it. Very convenient!

This feature could be extended to include a Download option on submission pages.

Especially nice to have for week-long contests with individual timers.

Possible implementation idea includes introducing a new Solution view, possibly with its own model, that leverages our commenting system.

Another idea could be replacement flatpage views and middleware which actually have working comments.

Either way the implementation shouldn't be too hard. (famous last words)

Current navigation bar uses nested template. We should give django-mptt a try.

Random errors about judges being dead, e.g. Judge seems dead: Iodine: 49880. Happens after wrong acknowledge for this iodine case.

Different cause on Berlin:

INFO 2015-02-26 00:57:23,299 judgelist Queued submission: 48558
INFO 2015-02-26 00:57:26,220 judgelist Dispatched queued submission 48558: Berlin
ERROR 2015-02-26 00:58:04,988 judgehandler Judge seems dead: Berlin: 48558

When wbox crashes, its generated accounts are never cleaned. They should be cleaned the next time the judge boots.

C:\Users\Tudor>net user

User accounts for \\BERLIN

-------------------------------------------------------------------------------
Administrator            Guest                    Tudor
-----------              wbox0000000000c6afaf     wbox0000000001871be0
wbox00000000018a93b8     wbox000000000191d021     wbox0000000001aa8ccc
wbox0000000001b196a0     wbox000000000ace72e2     wbox000000000b23e734
wbox000000000b296475     wbox000000000b324dc7     wbox000000000ba9c9f5
wbox000000000bb804e8     wbox000000000bbb3434
The command completed successfully.

The feature introduced in #20 is inconsistent with the resubmission feature as a user. In particular, the Resubmit link does not appear on the source page for a user submission.

As the size of these pages continue to grow, sooner or later they will impossible to send as one page. I suggest we start to encode various sorting options in the URL in anticipation of pagination, and may be experiment pagination on the users page.

For #40, it would be a lot nicer to have an extension field on the Language model so we can generate file names.

For those people always complaining DMOPC starts too early, allow people to start at both a fixed time or at their own time. Possibly separate scoreboards for both kinds of people, or merge them both with a special indicator for virtual participants (like a small tick next to their handle). Check out virtual participation from http://codeforces.com/contests for ideas.

A lot of wrong acknowledgement errors. Tell-tale sign is: Judge seems dead: Excalibur: False. False is the sentinel value for no submission.

Some have user selection and basically DoS's the user, namely the organization one. The problem one is due for deletion.

As for rating, like http://www.dmoj.ca/user/quantum/rating

Full name of user is displayed, unlike submissions pages where only username is.

I recall that @FatalEagle really wants to resubmit other people's submissions so he doesn't have to copy and paste. This could be arranged.

Implementation:

• One resubmit_other permission.
• The submit view should not 403 with that permission.
• The UI shows resubmit for those with permission.

Since django-reversion is pulled in due to #29, we can now use it to implement comment editing and public history. This has in fact been long promised.

Some problems may be licensed, in which case it would be good to have a general mode to display licenses, in the info-float or similar. For example, http://www.dmoj.ca/problem/origami

We could even store license texts on the DMOJ for easy reading.

We need a better way to store comments. May be https://github.com/django-mptt/django-mptt/ will help.

A huge list, show multiple times is not very good.

Some problems for which authors are known but don't posses a DMOJ account would benefit from the ability to link faux profiles as problem setters. For example, http://www.dmoj.ca/problem/origami

Hide submission username from other people? This feature could be useful

Remove all instances of the string dmopc in the site since it's now the DMOJ, not just some code to run the monthly DMOPC contest.

Translation: massive s/dmopc/dmoj/g crusade.