Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getting error 500 when trying to transfer repo from user to organization #10230

Closed
1 of 7 tasks
zuhairamahdi opened this issue Feb 11, 2020 · 6 comments
Closed
1 of 7 tasks

Comments

@zuhairamahdi
Copy link

  • Gitea version (or commit ref): 1.9
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

when trying to transfer a repo from a user to an organization we get error 500 (this is not always the case) as we transferred between organizations before.
...

Screenshots

@6543
Copy link
Member

6543 commented Feb 12, 2020

@zuhairamahdi i higly recomend to update gitea - can you test with 1.11.0 ?

@SonGokussj4
Copy link

Hi. I've got 1.11.0 (docker image) and the /repo/transfer through API is not in swagger and don't work at all with:

repo_data = {'new_owner': organization}
repo_headers = {'accept': 'application/json', 'content-type': 'application/json',
                'Authorization': 'token ACCESS_TOKEN'}
res = requests.post(
    f"{SERVER}/api/v1/repos/{username}/{reponame}/transfer?access_token={GITEA_TOKEN}",
    headers=repo_headers, json=repo_data)

When I tried latest (26d855b611b4154598b45c4ebc299b2d4c9ce03a47ef43d573cad8d109ed2387) version (I think 1.12.0-dev) it works just fine.

But the font was very bad so we're back on 1.11.0 for now.

@6543
Copy link
Member

6543 commented Feb 17, 2020

@SonGokussj4 the repo/transfere API is a feature of 1.12.x

@hrvoj3e
Copy link

hrvoj3e commented Feb 27, 2020

@SonGokussj4 the repo/transfere API is a feature of 1.12.x

Thanks for the hint.
#9947

@stale
Copy link

stale bot commented Apr 27, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Apr 27, 2020
@stale
Copy link

stale bot commented May 13, 2020

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed May 13, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants