"Noisy" containers lead to uncaught exception about broadway-api

[jasonB221]

WRT your second point, could you not add the validation to the DAO itself, so each DAO can decide whether or not it wants to continue execution or error out if the size is too large?

[ayushr2]

Yes as @nblei mentioned the two possible solutions we are looking at are:

• Adding a new optional field here in the grading stage called logs which is true by default. When set to false, the Broadway grader would discard the logs generated.
• MongoDB has a limit of 4MB (old versions) and 16MB (newest version) of document size. We could calculate log size on the broadway grader and if it is above 4MB, we save logs as:

{
    "stdout": "",
    "stderr": "Logs not saved because it was more than 4MB",
}

My concern with the second solution is that it is very Mongo specific while we have made an attempt to create a DAO layer so people could plug in other databases. #29

Thoughts @nmagerko @rod-lin @bhuvy2

[nmagerko]

Truncation and/or validation in the DAO seems like the way to go for extreme cases, but having a logs option in the grading stage sounds like a very reasonable thing to have as well.