github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-18 00:14:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

500 error when migrating with mirror #4117

New Issue
Closed
opened 2025-11-02 05:38:53 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 05:38:53 -06:00
Owner
Copy Link

Originally created by @wsand02 on GitHub (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.

Originally created by @wsand02 on GitHub (Oct 14, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.10.0+dev-433-gdb0d4ffdc - Git version: 2.17.1 - Operating system: Linux (Ubuntu 18.04) - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No Something was wrong with the site just received 500 erros - [ ] Not relevant - Log gist: https://gist.github.com/wilsandbrink/f12c802b7c76c2859e7bc42bb0c5939a ## 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. <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 05:38:53 -06:00
GiteaMirror commented 2025-11-02 05:38:54 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Oct 14, 2019):

do you use two-factor auth?

@6543 commented on GitHub (Oct 14, 2019): do you use two-factor auth?
GiteaMirror commented 2025-11-02 05:38:54 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Oct 14, 2019):

confirmed ... I'll try to fix it

@6543 commented on GitHub (Oct 14, 2019): confirmed ... I'll try to fix it
GiteaMirror commented 2025-11-02 05:38:54 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Oct 14, 2019):

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

@6543 commented on GitHub (Oct 14, 2019): @zeripath can you add bug and backport to 1.10.x lable?
GiteaMirror commented 2025-11-02 05:38:55 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Oct 15, 2019):

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

@lunny commented on GitHub (Oct 15, 2019): @wilsandbrink please confirm that #8526 will fix the issue.
GiteaMirror commented 2025-11-02 05:38:55 -06:00
Author
Owner
Copy Link

@wsand02 commented on GitHub (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 commented on GitHub (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](https://status.docker.com/pages/incident/533c6539221ae15e3f000031/5da5fc78c7b1c11cd8603721)).
GiteaMirror commented 2025-11-02 05:38:55 -06:00
Author
Owner
Copy Link

@wsand02 commented on GitHub (Oct 15, 2019):

@lunny #8526 fixed the issue.

@wsand02 commented on GitHub (Oct 15, 2019): @lunny #8526 fixed the issue.
GiteaMirror commented 2025-11-02 05:38:56 -06:00
Author
Owner
Copy Link

@wsand02 commented on GitHub (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 commented on GitHub (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.
GiteaMirror commented 2025-11-02 05:38:56 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Oct 15, 2019):

@wilsandbrink well noticed ...

@6543 commented on GitHub (Oct 15, 2019): @wilsandbrink well noticed ...
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/confirmed type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4117
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?