Importing a Git repository and setting the mirror option at the same time, results to the repository showing empty

Reported in https://gitlab.com/gitlab-com/support-forum/issues/539

Steps to reproduce

1. Pressed "New project" button in the upper right corner

• Wrote a name for the repo
• Pressed "Any repo by URL"
• Went over to GitHub and copied HTTPS clone URL for one of my repos
• Pasted the URL into "Git repository URL" field at GitLab
• Checked "Mirror repository" checkbox
• Wrote a short description
• Selected "Public" visibility level
• Pressed "Create project" button
• Waited for about 10 seconds while GitLab cloned the repo
• Observed the problem I'm reporting :)
• Waited for a couple hours in hope of problem resolving itself during mirror update (GitLab tells me those happen every hour)
• Updated the repo manually a couple of times

Milestone changed to 8.6

@Minoru-kun Thanks for reporting this! I've scheduled it for 8.6 so I don't lose track of it, but I will be taking a look at all scheduled issues in the next few days, so it may move to (a patch release to) 8.5.

mentioned in issue gitlab-com/support-forum#539 (closed)

Cool, thank you! Apparently I filed the issue to the wrong tracker? — sorry for that.

@yorickpeterse may have found a cache issue that affects both forking and mirroring/importing.

@Minoru-kun No, you reported it in the right place. You didn't know whether it was a GitLab.com bug or a GitLab application bug. We just moved it once we discovered it was an application bug.

Milestone changed to 8.7

Milestone changed to 8.8

Milestone changed to %8.9

I've also got this bug. Probably another caching issue since I can clone mirror and start builds.

Removed repository ~91797 mirror labels

Milestone changed to %8.10

Added ~360297 ~91797 mirror labels

@mati865 in which gitlab version?

Added repository label

I don't remember which at which version gitlab.com at time of writing but it's resolved now.

Milestone changed to %8.11

Status changed to closed