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

500 error when migrating with mirror #8514

Closed
2 of 7 tasks
wsand02 opened this issue Oct 14, 2019 · 8 comments · Fixed by #8526
Closed
2 of 7 tasks

500 error when migrating with mirror #8514

wsand02 opened this issue Oct 14, 2019 · 8 comments · Fixed by #8526
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Milestone

Comments

@wsand02
Copy link

wsand02 commented Oct 14, 2019

Description

If I migrate repository without mirroring it works fine and I get the new cloning interface. But if I mirror it I mean I still get the repo, it's just that I receive a 500 error. It's just a little annoying that's all.

Screenshots

Hard to screenshot.

@6543

This comment has been minimized.

@6543
Copy link
Member

6543 commented Oct 14, 2019

confirmed ... I'll try to fix it

@6543
Copy link
Member

6543 commented Oct 14, 2019

@zeripath can you add bug and backport to 1.10.x lable?

@zeripath zeripath added backport/v1.10 type/bug issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented labels Oct 15, 2019
@zeripath zeripath added this to the 1.11.0 milestone Oct 15, 2019
@lafriks lafriks modified the milestones: 1.11.0, 1.10.0 Oct 15, 2019
@lunny
Copy link
Member

lunny commented Oct 15, 2019

@wilsandbrink please confirm that #8526 will fix the issue.

@wsand02
Copy link
Author

wsand02 commented Oct 15, 2019

How do I test the version with the fix?
Edit: Nvm think I figured it out.
Just unable to build to the docker image atm due to 503 errors (seems to be related to this).

@wsand02
Copy link
Author

wsand02 commented Oct 15, 2019

@lunny #8526 fixed the issue.

@wsand02 wsand02 closed this as completed Oct 15, 2019
@wsand02
Copy link
Author

wsand02 commented Oct 15, 2019

Reopening issue until merged.

Edit: Someone can close this if they wan't since it is technically solved. Just wasn't sure if I was supposed to close it yet.

@wsand02 wsand02 reopened this Oct 15, 2019
@6543
Copy link
Member

6543 commented Oct 15, 2019

@wilsandbrink well noticed ...

@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.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants