drdab / launchtestrun Goto Github PK

It may be a good idea to add a forensic identifier to each submission and logging to identify the source of bugs and malicious attacks on a LaunchTestRun server. This should consist of a general log containing the IP address, time uploaded, code sent, execution time and stdin/out/err output from the code and compiler. That way, the sources of issues can be pinpointed faster by the sysadmin.

title

A timer should be added to force termination of program after 2 seconds if the program does not execute, whether it has finished or not. That way, if a program is too slow or keeps waiting for standard input, it won't eat up CPU time for long.

title

Add a JSON parameter in the config.json to specify strict or non-strict judging setting for a problem. (For problems that have multiple correct answers)

If a HashMap was to be used to map the problems complementing the ArrayList current used, it would be more efficient to reference problems. (Efficiency will go from O(n) worst-case to O(1) to access each problem).

A good idea would be to add a subsystem that limits the number code submission requests, to prevent exhaustion of resources. This system should grab the IP of the user submitting the code, and if it hasn't seen that IP yet, then save that IP to a list that is cleared every minute. Each time that upload is done again, it should increment the count of uploads that IP has done. Once the user has attempted to submit more than 6 uploads per minute, then uploads from that IP will be temporarily blocked until the next minute. Something like that could also be used, with a JSessionID cookie instead, for a "xx users online" counter.