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

Migration of a repo ends in 504 Gateway Time-out by nginx/1.14.2 #3991

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

Originally created by @jayjupdhig on GitHub (Sep 20, 2019).

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

Description

Migration of a repo ends in 504 Gateway Time-out by nginx/1.14.2, that's all what i can say...

Screenshots

dfwefef

...and when i try to delete the failed (on migration/mirroring) repo, i get a 500-error. And that will cause that i can't delete the failed repo anymore!!!!!

Screenshot here:

werter

WTF??

Originally created by @jayjupdhig on GitHub (Sep 20, 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): Most current - Git version: Most current - Operating system: Debian 10 "Buster" - Database (use `[x]`): - [ ] PostgreSQL - [ x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ x] Not relevant - Log gist: ## Description Migration of a repo ends in 504 Gateway Time-out by nginx/1.14.2, that's all what i can say... ## Screenshots ![dfwefef](https://user-images.githubusercontent.com/42765391/65335966-bbf5d000-dbc5-11e9-8622-7f12c84eb9cb.jpg) <!-- **If this issue involves the Web Interface, please include a screenshot** --> ...and when i try to delete the failed (on migration/mirroring) repo, i get a 500-error. And that will cause that i can't delete the failed repo anymore!!!!! Screenshot here: ![werter](https://user-images.githubusercontent.com/42765391/65336122-12fba500-dbc6-11e9-8fd3-93b06b886545.jpg) WTF??
GiteaMirror commented 2025-11-02 05:33:07 -06:00
Author
Owner
Copy Link

@jayjupdhig commented on GitHub (Sep 20, 2019):

Now it suddenly works - migration with option "mirror" was successful with the same (!!!!!) remote repo!

And: The failed repos was delete automatically.

Gitea seems to have tons of inconsistencies...

@jayjupdhig commented on GitHub (Sep 20, 2019): Now it suddenly works - migration with option "mirror" was successful with the same (!!!!!) remote repo! And: The failed repos was delete automatically. Gitea seems to have tons of inconsistencies...
GiteaMirror commented 2025-11-02 05:33:07 -06:00
Author
Owner
Copy Link

@jayjupdhig commented on GitHub (Sep 20, 2019):

How to get the logs to debug what happened and why?

@jayjupdhig commented on GitHub (Sep 20, 2019): How to get the logs to debug what happened and why?
GiteaMirror commented 2025-11-02 05:33:08 -06:00
Author
Owner
Copy Link

@jayjupdhig commented on GitHub (Sep 20, 2019):

The only one difference between the 1st (not successful with 504 and 500 errors) and the 2nd (successful!!) try is:

1st try: Initial commit on remote repo had comment: "initial commit"
2nd try: Initial commit on remote repo had comment "..."

?????????????????????????????

@jayjupdhig commented on GitHub (Sep 20, 2019): The only one difference between the 1st (not successful with 504 and 500 errors) and the 2nd (successful!!) try is: 1st try: Initial commit on remote repo had comment: "initial commit" 2nd try: Initial commit on remote repo had comment "..." ?????????????????????????????
GiteaMirror commented 2025-11-02 05:33:08 -06:00
Author
Owner
Copy Link

@jayjupdhig commented on GitHub (Sep 20, 2019):

Maybe there was a background process which caused that problem, i don't really believe that the inital commit's comment on the remote repo makes issues like that. That would be really strange...

The remote git server for mirroring can't be the problem - we use it since years with "SourceTree" - successfully and we never had such problems.

So it must be on Gitea level..

@jayjupdhig commented on GitHub (Sep 20, 2019): Maybe there was a background process which caused that problem, i don't really believe that the inital commit's comment on the remote repo makes issues like that. That would be really strange... The remote git server for mirroring can't be the problem - we use it since years with "SourceTree" - successfully and we never had such problems. So it must be on Gitea level..
GiteaMirror commented 2025-11-02 05:33:08 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Sep 30, 2019):

I have sent a PR #6200 to try to fix this.

@lunny commented on GitHub (Sep 30, 2019): I have sent a PR #6200 to try to fix this.
GiteaMirror commented 2025-11-02 05:33:08 -06:00
Author
Owner
Copy Link

@jayjupdhig commented on GitHub (Sep 30, 2019):

ok thx

@jayjupdhig commented on GitHub (Sep 30, 2019): ok thx
GiteaMirror commented 2025-11-02 05:33:09 -06:00
Author
Owner
Copy Link

@jayjupdhig commented on GitHub (Oct 3, 2019):

How can i see on what release version that fix is integrated? Thank you for your feedbacks.

@jayjupdhig commented on GitHub (Oct 3, 2019): How can i see on what release version that fix is integrated? Thank you for your feedbacks.
GiteaMirror commented 2025-11-02 05:33:09 -06:00
Author
Owner
Copy Link

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

last stable release is 1.9.3 as https://github.com/go-gitea/gitea/releases tells you ...
and if I understand lunny right he like to have implemented the "background-migration" in v1.10.x ...

@6543 commented on GitHub (Oct 3, 2019): last stable release is 1.9.3 as https://github.com/go-gitea/gitea/releases tells you ... and if I understand lunny right he like to have implemented the "background-migration" in v1.10.x ...
GiteaMirror commented 2025-11-02 05:33:09 -06:00
Author
Owner
Copy Link

@guillep2k commented on GitHub (Oct 3, 2019):

Issue #6200 was recently moved from milestone 1.10.0 to 1.11.0. It doesn't mean that it couldn't be added to some 1.10.x along the way.

@guillep2k commented on GitHub (Oct 3, 2019): Issue #6200 was recently moved from milestone 1.10.0 to 1.11.0. It doesn't mean that it couldn't be added to some 1.10.x along the way.
GiteaMirror commented 2025-11-02 05:33:10 -06:00
Author
Owner
Copy Link

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

I moved #6200 because I found we could also migrate repos from github even if we have not background migrating implementation. To move forward v1.10, so I move it to v1.10.

@lunny commented on GitHub (Oct 4, 2019): I moved #6200 because I found we could also migrate repos from github even if we have not background migrating implementation. To move forward v1.10, so I move it to v1.10.
GiteaMirror commented 2025-11-02 05:33:10 -06:00
Author
Owner
Copy Link

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

@martijintro is your question/issue solfed

@lunny you mean 1.11.?

@6543 commented on GitHub (Oct 4, 2019): @martijintro is your question/issue solfed @lunny you mean 1.11.?
GiteaMirror commented 2025-11-02 05:33:10 -06:00
Author
Owner
Copy Link

@jayjupdhig commented on GitHub (Oct 4, 2019):

yes

@jayjupdhig commented on GitHub (Oct 4, 2019): yes
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
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#3991
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?