Migration with pull requests from other gitea instance fails

[lakostin]

• Gitea version (or commit ref):
  1.14.0+dev-18-gd453533be
• Git version:
  2.26.2
• Operating system:
  docker Alpine Linux
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
• Log gist:
  2020/10/22 13:25:46 ...ules/task/migrate.go:64:func1() [E] DeleteRepository: repository does not exist [id: 208, uid: 75, owner_name: , name: ]
  2020/10/22 13:25:46 modules/task/task.go:51:handle() [E] Run task failed: error while loading reactions: 403 Forbidden

Description

Migration without pull requests works fine for the same repo.
...

[6543]

looks like the account do not have access to the reactions endpoint ... - witch version the gitea instance you are migrationg from has?

[lakostin]

looks like the account do not have access to the reactions endpoint ... - witch version the gitea instance you are migrationg from has?

same version - 1.14.0+dev-18-gd453533be

[6543]

@lakostin can you tell me the url from the source, or send it to me via email if it should not get public?

[lakostin]

@lakostin can you tell me the url from the source, or send it to me via email if it should not get public?

impossible cause it's in private network

[6543]

hmm I'll try to reproduce it somehow

[6543]

@lakostin sorry could not reproduce it for now ...

[lakostin]

@lakostin sorry could not reproduce it for now ...

i tried to migrate three different pull requests and all of them failed. maybe its connected with migrations during gitea update? Firstly i had an installation of 12 version of gitea and constantly updated it until the 14 version. is there any way to check it? maybe check db relations?

[lakostin]

@6543 ?

[6543]

@lakostin you can use the "doctor" command to check and fix things (./gitea doctor --help)

and two question:

• can you see the diff via web ui on this pulls?
• was this repository already migrated from another gitea/github/... in the past?

[lakostin]

@lakostin you can use the "doctor" command to check and fix things (./gitea doctor --help)

and two question:

• can you see the diff via web ui on this pulls?

yes, diff works fine for all pull requests in all these projects

• was this repository already migrated from another gitea/github/... in the past?

no, all the repos are new

[6543]

@lakostin

... had an installation of 12 version of gitea and constantly updated it until the 14 ...

do you mean v1.12.x to v1.14.0+dev ?

If so what version sha is displayed? (example try.gitea.io show 1.14.0+dev-100-g946bbbe9b)