Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Internal Server Error 500 When Accessing an Assignment in GitHub Classroom #1117
Hello! Thank you so much for developing GitHub Classroom. So far, my students and I have really enjoyed using the system. In advance of running the laboratory session today, I have tested it repeatedly with small class sizes for our first laboratory assignment and everything always worked correctly.
That is, it was possible to:
However, today when I had 40 people follow the last three steps in this list I could no longer see the
I see a message that declares "Internal Server Error" and then error code 500. It turns out that I have never seen this error after testing GitHub Classroom with the same assignment for approximately the past 1-2 weeks. However, when I was previously testing these steps, there were never more than three students working on the assignment.
I have tried to access the GitHub Classroom and the specific assignment, which is at:
and all of those screens always appear correctly. However, when I specifically try to see the assignment submissions for the first laboratory assignment, I always see the aforementioned error.
I have tried these links using both Chrome and Firefox and I always see exactly the same error message. I also see the same error message even when I use different computer. For what is is worth, I have also created a class roster with email addresses but not yet associated the email addresses with the GitHub account for each student; I planned to do that today but could not because I saw the 500 error message.
I should also note that I quickly searched the lists of issues for GitHub Classroom and did not immediately see that this type of issue was already submitted; it if was, please point me in the right direction and I will take steps to try to further solve this matter.
Okay, I hope that this helps you to better understand the context and the error that I am experiencing.
If your schedule permits, can you get back to me with a step that I could take to debug the issue further or to resolve it fully? Since I am not running GitHub Classroom on Heroku, but instead using your installation and server it seems that I may need this issue to be resolved before I can grade these assignments. Of course, please let me know if there is anything that I can do to support the resolution of this issue!
I believe I have the same issue.
I have a 500 error on one of my assignments; it's also the first assignment (here) in my classroom.
Wondering if it may be related to creating a class roster?
My other assignments are all viewable normally.
I have the same issue. I created and assignment and created a class roster.
Everything was fine at first. Now I have 25 students who have submitted their assignments and when I click on either the assignment (to open the assignment page) or when I open "Classroom Management" and click on "Roster Management" I get a 500 error.
If you're curious the massive PR is here: #1127
I've gone through and verified for each of your accounts that everything is working properly, please let me know if you run into any other issues.
Thanks again for your patience.
Hello @tarebyte! Thanks for making this fix. I noticed #1127 and then immediately checked to see if the "Internal Server Error" was resolved. I am delighted to report that it seems to be fixed now. Thanks for taking time over your weekend to work on this issue. @minneapolis-edu and @jonathan-g, do you also notice that the error has been resolved?
Finally, is there anything that I might have done to cause the server to get into this incorrect internal state? That is, do I need to avoid using GitHub Classroom in some way so that this does not happen again? My understanding is that #1127 resolves the issue and I can continue as before. But, please let me know if that understanding is not correct.
Thanks again! Your help is greatly appreciated!
It's working. Thanks!…
On Mon, Feb 5, 2018, 10:58 PM Mark Tareshawty ***@***.***> wrote: @dwrue1 <https://github.com/dwrue1> we had a bad deploy which I've reverted, would you mind checking it out to see if your issue has resolved? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1117 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AhamFT_7iX1nIjpAMH3J8OotMeXVtQjoks5tR83fgaJpZM4PJcqk> .
I am facing the same issue again. Would it be possible for you or someone on your team to check it?