You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears it is too easy to mistake the "Student Files" section in project configuration for "Student Lookup".
When someone accidentally tries to look up a student in "Student Files", their uniqname gets added as a required file.
Of course, this interferes with students submitting the project. At the same time, the poor student who someone was trying to look up has their uniqname plastered on Piazza as people post the error message they're getting.
The interface is clear to me, but perhaps only because I have the advantage of extensive experience configuring the autograder. I suggest a change to the UI to prevent this. Two ideas:
Add a bold, ugly warning to the UI that "THIS IS NOT STUDENT LOOKUP" when you're on the "Student Files" config tab.
If a project is currently published, the frontend UI makes changing student files more involved. For example, it could disable the "Add File" button unless you check a box that says something like "yes I know what I'm doing and I really want to add a new file that all students must submit".
1 is less work, but 2 is probably a better solution.
The text was updated successfully, but these errors were encountered:
It appears it is too easy to mistake the "Student Files" section in project configuration for "Student Lookup".
When someone accidentally tries to look up a student in "Student Files", their uniqname gets added as a required file.
Of course, this interferes with students submitting the project. At the same time, the poor student who someone was trying to look up has their uniqname plastered on Piazza as people post the error message they're getting.
The interface is clear to me, but perhaps only because I have the advantage of extensive experience configuring the autograder. I suggest a change to the UI to prevent this. Two ideas:
1 is less work, but 2 is probably a better solution.
The text was updated successfully, but these errors were encountered: