Assignment repository setup hanging

[timalcon]

Describe the bug I’m having several students report that when they try to set up an assignment repository, it just hangs, with no change in the progress bar. This is a new problem - it worked for them previously.

To Reproduce Steps to reproduce the behavior:

1. Click on GitHub Classroom link
2. Click "Accept this assignment"
3. Wait in vain for progress bar to change It doesn't happen for me, who owns the Classroom account, but started happening for students a day or two ago.

Expected behavior The progress bar should complete and say "you're ready to go".

Screenshots

[dominicwhite]

This is also happening for me. So far just one student out of a class of 20, but he also gets the same issue for another Github classroom invitation in another organization.

Edit: a second student is now having the same issues.

[kesttvanzyl]

I am having the same issue. I have tried opening two assignments and both of them are stuck on the progress bar. I left the page open for about an hour and it is still just hanging without showing any progress in the progress bar.

[robwhess]

Some of my students are also experiencing this. Sorry not to add any new information other than that. Just trying to increase urgency on this issue 😸

[ethantmcgee]

One of my students @ELANE931 is also having an issue cloning his assignments so I've been manually creating the repos for him in the mean time.

[danwallach]

This sounds like a common problem using the "original" clone link process. The new "template" process has been much more robust for me. Make sure you try that.

[ethantmcgee]

@danwallach My group has converted our classrooms over to the template system, and I still have a few random students that are having issues.

[robwhess]

Yes, I can confirm that I'm also using template repos for my starter code, and students are still experiencing this problem.

When my students used to have a problem with repository creation hanging under the original non-template system, it was almost invariably the case that a repo had been created for them on GitHub, but for some reason the code had failed to import. To fix the problem, I could usually just go and delete the (empty) repo that was created for them, and then when they accepted the assignment a second time, everything would work fine.

In these last few instances, however, where the repo creation process hung using the new template repo system, there wasn't even a GitHub repo (empty or not) created for the students in question. This makes me think the hanging in this case is happening earlier in the repo creation process than it used to, maybe even on the client side, but at least before any GitHub API calls are made to actually create the new repo (or possibly there's a failure with those API calls themselves).

[stephaniegiang]

@robwhess could you tell us the classroom name and assignment this is happening in?

[robwhess]

Sure, @stephaniegiang, the classroom is osu-cs261-f19:

https://classroom.github.com/classrooms/55517190-data-structures-cs-261-oregon-state-fall-2019

The specific assignment I know students are seeing this problem with is Assignment 2:

https://classroom.github.com/classrooms/55517190-data-structures-cs-261-oregon-state-fall-2019/assignments/assignment-2

[dominicwhite]

I just had another student with the same issue in the Edge browser, but they were able to get their repository created by switching to Chrome.

[psybers]

This is happening to me too. The classroom is BGSU-CS-3060-F19.

[psybers]

I can confirm switching from Edge to Chrome fixed it for my student.

[stephaniegiang]

Has retrying after waiting for a bit helped anyone?

[dominicwhite]

@stephaniegiang My first student was able to get it working after he went home, but I now wonder if that's because he was using a different (up-to-date?) browser on a different computer, rather than because of waiting.

[spinecone]

Since there have been multiple reports of this problem being resolved after switching from Edge to Chrome, has anyone experienced this problem on Chrome?

[robwhess]

The one student who gave me more details about the problem said they experienced the problem on both Edge and IE and that everything worked fine when they switched to Chrome. Sounds like an MS thing!

[spinecone]

While we're working on resolving this, we recommend that folks running into this problem try again on Chrome and let us know if they're still seeing issues.

[d12]

Hey all, this should be resolved now. We're going to dig into why this wasn't raised by our metric systems earlier, thanks for the patience!