I didn't know if issue for gitlab.com placed in Community Edition, since it run on Gitlab Enterprise Edition.
Can we add somewhere in about.gitlab.com where to report if we encounter a problem?
@tanperkis Did you download the Gitea binary from dl.gitea.io? Otherwise I'd need the commit sha you're running to debug it. Also it would help if you pasted the logs from Gitea here :)
[Macaron] 2017-04-27 20:25:18: Started GET /api/v1/user/repos for 52.184.195.32[Macaron] 2017-04-27 20:25:18: Completed /api/v1/user/repos 200 OK in 31.582623ms[Macaron] 2017-04-27 20:25:35: Started GET /api/v1/rate_limit for 52.184.195.32[Macaron] 2017-04-27 20:25:35: Completed /api/v1/rate_limit 404 Not Found in 5.603137ms[Macaron] 2017-04-27 20:25:36: Started GET /api/v1/repositories/32 for 52.184.195.32[Macaron] 2017-04-27 20:25:36: Completed /api/v1/repositories/32 200 OK in 14.093966ms[Macaron] 2017-04-27 20:25:44: Started GET /tommy/TODOLIST.git/info/refs?service=git-upload-pack for 13.77.99.29[Macaron] 2017-04-27 20:25:44: Completed /tommy/TODOLIST.git/info/refs?service=git-upload-pack 401 Unauthorized in 2.09202ms
I already using gitea-1.1.0+144-g431b26f-linux-amd64 version but still failed. from the log
[Macaron] 2017-04-29 13:33:47: Started GET /api/v1/repositories/25 for 52.184.198.203[Macaron] 2017-04-29 13:33:47: Completed /api/v1/repositories/25 200 OK in 18.22334ms[Macaron] 2017-04-29 13:33:55: Started GET /tanperkis/website.git/info/refs?service=git-upload-pack for 40.70.218.101[Macaron] 2017-04-29 13:33:55: Completed /tanperkis/website.git/info/refs?service=git-upload-pack 401 Unauthorized in 1.620752ms
Another issue when testing using gitlab's gitea import :
I can't cancel current Gitea import or create another gitea import since it's always redirected me to https://gitlab.com/import/gitea/status, I must logout and login again to able to import gitea again.
No way to hide failed/retry imported repository, It's always there
if gitea services down Gitlab only show 500 Error page, the first I think gitlab down, but after some test I know my gitea server down for some reason
No way to re-import failed repository import, from few testing I only able to import not-yet imported gitea instance
after all failed test, I'll import my repository manually.
I am observing the same issue trying to import repositories from our gitea instance to the gitlab instance. I tried various versions of gitlab. Using try.gitea.io and gitlab.com, it says failed but it seems as if everything was imported. Using the exact same version of gitea on our local instance doesn't import anything.
Are there any new insights into this? I can't seem to finde any error message indicating what goes wrong here, neither on the gitea, nor on the gitlab side.
Thanks for the possibility to import from Gitea to GitLab. I'm using GitLab CE 9.5.3 and Gitea 1.2.0+rc1-6-g002fa73. GitLab tells me that the import failed.
But almost everything is imported: repository, labels, milestones, merge requests. But what I'm badly missing are the issues and that's basically the reason, why I want to use the import and not just pushing the files.
Update: It looks like the importer does not call the gitea api to retrieve the issues.