Question: Problem with Student's Repo


(Sam Black) #1

I’ve had an issue that’s popped up a couple of times (rare but annoying) where a student accepts an assignment but something happens while their copy of the repo is being created and it just never actually happens.

Anyone else have this problem?

Anyone know a solution?

I can say that going back and re-accepting the assignment doesn’t help.


(Scott Sanicki) #2

Hi Sam,

Can you check the GitHub Classroom repository for similar open issues:

Please add your experience to the relevant issue.

Thanks,
Scott


(Samuel Lijin) #3

I’ve had this too. The workaround has been either (1) delete the repository, re-accept the assignment, or (2) manually clone the skeleton and force-push to the failed repository.


How do students submit their assignments?
(Jcross Class) #4

This has been happening to me more often lately. I also accept my own assignment to make sure everything is good, and it happened to me during my testing once. I’ve been telling my students to let me know when it happens. The repository gets created, but it’s empty. I manually seed their repository with an initial push. It’s pretty annoying, but so far it only happens to 1 or 2 out of 25 students per assignment.


(Matthias) #5

I also had this problem today, too. About 20% of students couldn’t import the task I set them. I used import code from another repository to get the work from my original repository to the students that way.
The good thing about doing it this way is that I can do it from my machine for all failed imports. Failed imports are easy to spot as they show with “0 commits” in the list.


(Vanessa) #6

@memm74 we’re doing an audit of all Classroom issues in the next month or so. Please stay tuned and appreciate everyone opening an issue with their bug reports.


(Matthias) #7

Just an observation. I usually either have no problems at all or many students are affected. In that case importing the files into the student space is even very slow as if the servers are too busy.


(Vanessa) #8

Thank you for letting us know.