Error - FindRecentlyPushedNewBranches, branch does not exist [repo_id: 64 name: main]

[Flagelmann]

Description

I'm getting a weird issue on several repositories.

The actual error is a 500 error:

FindRecentlyPushedNewBranches, branch does not exist [repo_id: 64 name: main]

How to solve this? Should I modify the branch name directly on DB side? Is there any way to fix this from the Gitea web portal?

Actually, it seems that this new version has broken several repos at once. Until last week everything was good, clean and accessible. Now I'm getting this error on several repositories.

Gitea Version

1.22.0

Workaround

It has been fixed in 1.22-nightly (which will be 1.22.1 soon), please use the 1.22-nighly binary (https://dl.gitea.com/gitea/1.22-nightly/) or docker image.

[lunny]

Please try to run sync branches on admin panel.

[Flagelmann]

Yout mean the "Resynchronize pre-receive, update and post-receive hooks of all repositories."?

I have already tried multiple times it....nothing changed.

I also tried "Reinitialize all missing Git repositories for which records exist" under "Site Administration", nothing even with this.

I wish I will not have to rebuild the gitea instance from scratch.....so, re-import manually over 100 repositories (over 30 GB of data) and then also re-enable manually, by modifying manually each repository on database side the mirroring settings for each repo I have (as Gitea does not still have the way to backup these settings)....

[wxiaoguang]

Please try to run sync branches on admin panel.

I do not think FindRecentlyPushedNewBranches logic is right. Anything wrong in that function shouldn't block end users seeing a complete page.

[lunny]

Yout mean the "Resynchronize pre-receive, update and post-receive hooks of all repositories."?

I have already tried multiple times it....nothing changed.

I also tried "Reinitialize all missing Git repositories for which records exist" under "Site Administration", nothing even with this.

I wish I will not have to rebuild the gitea instance from scratch.....so, re-import manually over 100 repositories (over 30 GB of data) and then also re-enable manually, by modifying manually each repository on database side the mirroring settings for each repo I have (as Gitea does not still have the way to backup these settings)....

No. It's Sync missed branches from git data to databases

[Flagelmann]

I get, not for all repositories (fortunately), a Gitea error page with a big "500" at center page and then, just below, the message:

An error occurred:

FindRecentlyPushedNewBranches, branch does not exist [repo_id: 64 name: main]

Nothing else.

[Flagelmann]

Even with "Sync missed branches from git data to databases" nothing changed. It starts, but then nothing...

[lunny]

I get, not for all repositories (fortunately), a Gitea error page with a big "500" at center page and then, just below, the message:

An error occurred:

FindRecentlyPushedNewBranches, branch does not exist [repo_id: 64 name: main]

Nothing else.

The sync will take some times, maybe you need to wait for a while and refresh the page again.

[wxiaoguang]

As a quick fix: Ignore FindRecentlyPushedNewBranches err #31164

If you could build your own instance, you could try to apply it to 1.22 branch.

Or when the backport is done and 1.22-nightly is ready, please try 1.22 nightly.

[Flagelmann]

I am using snapcraft to deploy and get updates of Gitea.

May I get the nightly build with snap or do I have just to wait the next build?

[yp05327]

As a quick fix it is ok, but I think the root reason is that sync branch has some problems.
The branch name is main, so it is default branch of repo 64?
Then what kind of this repo is? A fork, a mirror or a normal one?
Then why this branch can not be found in DB? During the creation of this repo, the main branch should has been insert into the DB.