Students erroneously show up as having "Not submitted"

[sfikas]

Issue

What you were trying to do ?

I had created an assignment, of which the deadline passed recently. I wanted to check on the submitted assignments.

What happened (include screenshot if you can) ?

Several students show up as having "not submitted", while their repositories include a number of commits.

Step-by-step reproduction instructions

Please provide as much explanations as you can, reproduce a bug is the first step to write a fix 🙌
I opened the page that shows submissions for my assignment: https://classroom.github.com/classrooms/23520047/assignments/vision-set-2

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[floe]

I seem to have the same issue (see https://classroom.github.com/classrooms/9211630-mobile-media-group/group-assignments/se-ws18-exercise-2 ). In fact, all student repos show up as "(!) Not Submitted", regardless of whether they have committed something or not.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

[sunnypatel165]

We saw this as part of one of our classes too - https://classroom.github.com/classrooms/39249536-web-technologies-spring-2020/assignments/homework3?query=xudo&sort_by=Student%20identifier

[d12]

👋 @sunnypatel165 , did your student make any commits before the deadline? I see the deadline was 5 days ago, "Not submitted" either means no commits were made, or all were after the deadline. You can check by checking the GitHub repository commit history.

[sunnypatel165]

Yes, their commits were made 13 days ago.

[d12]

Great, it sounds like the feature is working as intended then 👍

[sunnypatel165]

@d12 - Sorry, How is this working as expected? The deadline was 5 days ago and the commits were 13 days ago.

So they DID submit before the deadline but still marked as not submitted. I think there is a bug.

[d12]

Ah I see! I misread your comment, oops. I'll ping the engineering team to peek at this soon.