Bugs Everywhere Bug List

Bug: e9e/330

ID : 3306d990-c9a9-4e6e-8059-1fac5a1bfb06
Short name : e9e/330
Status : open
Severity : minor
Assigned :
Reporter : adam j hartz <hz@mit.edu>
Creator : adam j hartz <hz@mit.edu>
Created : Tue, 28 May 2019 12:40:30 +0000
Target : v2019.9
Summary : improve UI when an error occurs during page load from checker

Comment: --------- Comment ---------
ID: ed8dd2c9-b04a-4051-8098-3edcce60a3ec
Short name: e9e/330/ed8
From: adam j hartz <hz@mit.edu>
Date: Tue, 28 May 2019 12:49:03 +0000

When the checker is loading a page or trying to find the question that someone
submitted to, there are rare cases where an error can occur.  Right now, the UI
continues to report that "your submission is currently being checker" in that
case, which is not true (since the error means we can't even start checking in
that case).    Example: 6.009 staff trying to submit `'q000000'` as a student,
but the student doesn't actually have that box because `cs_post_load` removes it
from their view.    Server reports:

    Process Process-173:
    Traceback (most recent call last):
      File "/usr/lib/python3.5/multiprocessing/process.py", line 249, in _bootstrap
      File "/usr/lib/python3.5/multiprocessing/process.py", line 93, in run
        self._target(*self._args, **self._kwargs)
      File "checker.py", line 148, in do_check
        question, args = namemap[name]
    KeyError: 'q000000'

Comment: --------- Comment ---------
ID: f37d7c53-2105-46bb-9cf5-3f71acbaab57
Short name: e9e/330/f37
From: adam j hartz <hz@mit.edu>
Date: Tue, 28 May 2019 12:52:51 +0000

PR #83 implemented a temporary fix for this, but there is still work to be done
here.  Rather than the catch-all that's currently implemented, it would be good
to carefully `try` the different pieces associated with loading a page so we
can give a better error message than "an unexpected error occurred".