Crashing from threads #11
Description
I'm sure this probably can happen a few places, but recently discovered a specific case where a side thread crashes and causes cryptic crashes.
A better handling of thread crashes (better exception handling, providing useful messages) could be good. As this tool will probably only live for one more semester, it's probably not worth fixing, but figured I'd document this anyway.
This was in doing an unmatched student report. The zybook report was missing an expected field, so the report fetching thread threw an uncaught exception (at grade_puller.py:312) - this caused the thread to die, and allowed the WorkerThread it was held in to return a result of None, which caused later issues in the primary thread.
Turns out in this case that the option in the zybook to "Require Student IDs" was not enabled, and doing so added the "Student ID" field to the zybook reports and allowed proper functioning.