Migration: migrating migrated repo fail #6200

New Issue

GiteaMirror · 2025-11-02T06:48:06-06:00

GiteaMirror commented

2025-11-02 06:48:06 -06:00

Originally created by @6543 on GitHub (Oct 22, 2020).

Originally assigned to: @6543 on GitHub.

while try to migrate from gitea ( 1.14.0+dev-63-g26d6c1530) to gitea (1.14.0+dev-44-gf0fe5683f) a db deadlock ocure (mysql)

source repo: https://try.gitea.io/abcKing/GitNex

Originally created by @6543 on GitHub (Oct 22, 2020). Originally assigned to: @6543 on GitHub. while try to migrate from gitea ( 1.14.0+dev-63-g26d6c1530) to gitea (1.14.0+dev-44-gf0fe5683f) a db deadlock ocure (mysql) source repo: https://try.gitea.io/abcKing/GitNex

GiteaMirror added the topic/repo-migration type/bug labels 2025-11-02 06:48:07 -06:00

GiteaMirror closed this issue

2025-11-02 06:48:07 -06:00

GiteaMirror commented

2025-11-02 06:48:07 -06:00

@zeripath commented on GitHub (Oct 23, 2020):

Dude!! Seriously this is a bad bad bad issue report!

I presume you mean that you were trying to migrate the repository https://try.gitea.io/abcKing/GitNex from try.gitea.io to a local server and the local server deadlocked? Or do you mean that try deadlocked?

I'm guessing you meant your local server's database is MySQL? ~~(I note try uses MySQL too)~~ Appears I was incorrect here try uses SQLite (thanks @lunny)

Do you have any logs around this point?

Are you sure it's a DB deadlock and not some kind of http loop or other code deadlock? MySQL should have a deadlock breaker meaning that at least one of the deadlocking queries/transactions should get broken.

Have you repeated the procedure with:

[database]
LOG_SQL=true
...

to get the SQL logs for this?

@zeripath commented on GitHub (Oct 23, 2020): Dude!! Seriously this is a bad bad bad issue report! I presume you mean that you were trying to migrate the repository https://try.gitea.io/abcKing/GitNex from try.gitea.io to a local server and the local server deadlocked? Or do you mean that try deadlocked? I'm guessing you meant your local server's database is MySQL? ~~(I note try uses MySQL too)~~ Appears I was incorrect here try uses SQLite (thanks @lunny) Do you have any logs around this point? Are you sure it's a DB deadlock and not some kind of http loop or other code deadlock? MySQL should have a deadlock breaker meaning that at least one of the deadlocking queries/transactions should get broken. Have you repeated the procedure with: ```ini [database] LOG_SQL=true ... ``` to get the SQL logs for this?

GiteaMirror commented

2025-11-02 06:48:07 -06:00

@lunny commented on GitHub (Oct 23, 2020):

@zeripath try uses sqlite, so it's easy to let the DB deadlock.

@lunny commented on GitHub (Oct 23, 2020): @zeripath try uses sqlite, so it's easy to let the DB deadlock.

GiteaMirror commented

2025-11-02 06:48:08 -06:00

@6543 commented on GitHub (Oct 23, 2020):

I'll shuld be more specific 😓 - but do not have logs at the moment, so I only can gess ...

... I'll work on this issue - and if I konw more I'll let you konw

@6543 commented on GitHub (Oct 23, 2020): I'll shuld be more specific :sweat: - but do not have logs at the moment, so I only can gess ... ... I'll work on this issue - and if I konw more I'll let you konw

GiteaMirror commented

2025-11-02 06:48:08 -06:00

@zeripath commented on GitHub (Oct 23, 2020):

no worries - it's just that if a user had made this report we'd be all stuck scratching our heads!

@zeripath commented on GitHub (Oct 23, 2020): no worries - it's just that if a user had made this report we'd be all stuck scratching our heads!

GiteaMirror commented

2025-11-02 06:48:08 -06:00

@6543 commented on GitHub (Oct 25, 2020):

@zeripath I have an error loged 🎉 - thanks for the error screen on migrations :)

Error 1062: Duplicate entry '+1-13037-0-1--1' for key 'UQE_reaction_s'

@6543 commented on GitHub (Oct 25, 2020): @zeripath I have an error loged :tada: - thanks for the error screen on migrations :) `Error 1062: Duplicate entry '+1-13037-0-1--1' for key 'UQE_reaction_s'`

GiteaMirror commented

2025-11-02 06:48:08 -06:00

@6543 commented on GitHub (Oct 25, 2020):

so I guess: since source repo is already a migrated repo: api returns some entrys who make no sence

the question is how to treat them: drop/show as GhotUser/ ?!?

@6543 commented on GitHub (Oct 25, 2020): so I guess: since source repo is already a migrated repo: api returns some entrys who make no sence the question is how to treat them: drop/show as GhotUser/ ?!?

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#6200