if blanks doesn't exist, blanks is then being made in supervisor, that's what is coded now.
But let's say it does create its empty blanks dir, and then a student comes up that really hasn't submitted a needed file. The system then goes to get the blank one and copy it over but it doesn't exist, so even though you made the blank dir, you didn't actually fix the problem.
Solution 1: halt he process from the get go if the blanks folder isn't filled in with the appropriate blank files (we will know the appropriate ones since we have the list of injections in the YAML file).
Solution 2: do not halt the program, wait till you hit a student like that, separate that student into a separate submissions folder, continue on to the next student. That way you can deal with it later or if there isn't that too many students, do it by hand.
if blanks doesn't exist, blanks is then being made in supervisor, that's what is coded now.
But let's say it does create its empty blanks dir, and then a student comes up that really hasn't submitted a needed file. The system then goes to get the blank one and copy it over but it doesn't exist, so even though you made the blank dir, you didn't actually fix the problem.
Solution 1: halt he process from the get go if the blanks folder isn't filled in with the appropriate blank files (we will know the appropriate ones since we have the list of injections in the YAML file).
Solution 2: do not halt the program, wait till you hit a student like that, separate that student into a separate submissions folder, continue on to the next student. That way you can deal with it later or if there isn't that too many students, do it by hand.