Repository migrate has internal server error but no message to indicate the problem #552

New Issue

kamandroid · 2021-11-03T20:40:32Z

kamandroid commented

2021-11-03 20:40:32 +00:00

#1. Not sure if bitbucket is supported

#2. Here is the postman (btw removed the sensitive info)

POST http://localhost:3000/api/v1/repos/migrate
500
10.57 s
POST /api/v1/repos/migrate HTTP/1.1
Authorization: Basic Z3Jhdml0eTpiRHl5eFFOTVpSVEVTZlJtQ3dnNQ==
Content-Type: application/json
User-Agent: PostmanRuntime/7.28.4
Accept: */*
Cache-Control: no-cache
Postman-Token: 9256e874-2aa9-44c7-8289-56f0ce2c5d2c
Host: localhost:3000
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Content-Length: 570
Cookie: _csrf=QDXBbU51eDKkMaMZHDKcFHfvE7Q6MTYzNTk3MDYyOTMzNTc1MzMzOQ; i_like_gitea=be9e51dee782ae7b
 
{
"repo_name": "MyFirstRepo",
"repo_owner": "kam",
"uid": 0,
"clone_addr": "mygitcloneaddress",
"service": "git",
"auth_username": "myusername",
"auth_password": "mypassword",
"auth_token": "",
"mirror": false,
"private": true,
"description": "This is my first repo",
"wiki": false,
"milestones": false,
"labels": true,
"issues": true,
"pull_requests": false,
"releases": true,
"mirror_interval": "",
"lfs": false,
"lfs_endpoint": ""
}

HTTP/1.1 500 Internal Server Error
Content-Type: application/json;charset=utf-8
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Date: Wed, 03 Nov 2021 20:19:06 GMT
Content-Length: 58
 
{"message":"","url":"http://gitea-http:3000/api/swagger"}

#1. Not sure if bitbucket is supported #2. Here is the postman (btw removed the sensitive info) ``` POST http://localhost:3000/api/v1/repos/migrate 500 10.57 s POST /api/v1/repos/migrate HTTP/1.1 Authorization: Basic Z3Jhdml0eTpiRHl5eFFOTVpSVEVTZlJtQ3dnNQ== Content-Type: application/json User-Agent: PostmanRuntime/7.28.4 Accept: */* Cache-Control: no-cache Postman-Token: 9256e874-2aa9-44c7-8289-56f0ce2c5d2c Host: localhost:3000 Accept-Encoding: gzip, deflate, br Connection: keep-alive Content-Length: 570 Cookie: _csrf=QDXBbU51eDKkMaMZHDKcFHfvE7Q6MTYzNTk3MDYyOTMzNTc1MzMzOQ; i_like_gitea=be9e51dee782ae7b { "repo_name": "MyFirstRepo", "repo_owner": "kam", "uid": 0, "clone_addr": "mygitcloneaddress", "service": "git", "auth_username": "myusername", "auth_password": "mypassword", "auth_token": "", "mirror": false, "private": true, "description": "This is my first repo", "wiki": false, "milestones": false, "labels": true, "issues": true, "pull_requests": false, "releases": true, "mirror_interval": "", "lfs": false, "lfs_endpoint": "" } ``` ``` HTTP/1.1 500 Internal Server Error Content-Type: application/json;charset=utf-8 X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN Date: Wed, 03 Nov 2021 20:19:06 GMT Content-Length: 58 {"message":"","url":"http://gitea-http:3000/api/swagger"} ```

kamandroid commented

2021-11-04 13:56:54 +00:00

After playing around with the pay load it appears that the internal server error 500 and no message on cause occurs if any of these value are set to true

"labels": true
"issues": true
"releases": true

So workaround is not bother setting those values

After playing around with the pay load it appears that the internal server error 500 and no message on cause occurs if any of these value are set to true "labels": true "issues": true "releases": true So workaround is not bother setting those values

lunny commented

2021-11-05 04:01:38 +00:00

Hm, It should be a bug of Gitea. When you migrate from a pure git service, all those are not supported.

lunny added the

upstream/gitea

label 2021-11-05 04:01:46 +00:00

Sign in to join this conversation.

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/go-sdk#552