Kyle Raftogianis
Kyle Raftogianis
Right now we show a "late submission" error. We should say instead that they're using the wrong course. We could help by displaying the error more prominently on the client...
We often forget to publish the "Regrade" tag, but that should not prevent regrade scores from being pushed to bCourses.
We have disputes with students who do not get emails. It would be helpful to have the scores both as a log and as feedback if students do not open...
Currently, we send emails one at a time to SendGrid, which is very slow. We should be able to send ~950 at a time instead, just swapping out the score...
We shouldn't be limited to a text log - each job should have a custom way to show its progress or eventual result. For example, our autograding job can display...
If a deploy happens during a job, it will just be left hanging when the worker is killed. Instead, kubernetes should send a signal to the worker requesting a warm...
Our jobs table is now ~100mB, and it's going to get bigger faster when we have repeated jobs. Jobs create a lot of output that could easily be compressed, so...
And how to write unlocking tests, release the distribution to students, etc.
The user needs to specify the assignment name, endpoint, and .py files. The generated assignment config would just be ``` { "name": "Homework 1", "endpoint": "https://okpy.org/path/to/endpoint", "src": [ "hw1.py", "hw1_extra.py"...
Our OK binary is now 1.4MB. We should have only one copy (e.g. in our `~/.config/ok` folder) and the "ok" file is just a script that invokes the shared code.