Abnormal synced commits and new reference records

[imkuang]

Description

Recently I observed some sync records on my Gitea instance as follows:

These records look abnormal (didn't appear before) and only appear in repos I mirrored from gitea.com (these mirrors have been around for a long time, I also have a lot of mirrors from github.com and they have no problems). So I'm not sure if this is a problem with my current version(1.23.5) or with the gitea.com version(1.24.0+dev-463-ge5bb8ba83b ?)

Gitea Version

1.23.5

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Official Docker image

Database

SQLite

[wxiaoguang]

IIRC not only one issue mentions that there are too many "mirror" activity records.

[imkuang]

I used to get a lot of sync records of pull request references from mirror repositories, such as refs/tags/refs/pull/130/merge or refs/pull/172/head, but they no longer appear (at least for github.com) on v1.23.5. I'm sure I've seen some pull requests for it, but I can't find them yet.

The problem I'm currently reporting is completely new, reference records like 1741518411097028371/tmp_refs/heads/main have never appeared before. I guess they are references used for some purpose inside gitea?

[imkuang]

I used to get a lot of sync records of pull request references from mirror repositories, such as refs/tags/refs/pull/130/merge or refs/pull/172/head, but they no longer appear (at least for github.com) on v1.23.5. I'm sure I've seen some pull requests for it, but I can't find them yet.

I found it, the previous issue was this: #27961

[lunny]

There refs are wired. Have you mirrored from https://gitea.com/gitea/act_runner ?

[imkuang]

There refs are wired. Have you mirrored from https://gitea.com/gitea/act_runner ?

Yes, the record in the screenshot is a mirror repo of https://gitea.com/gitea/act_runner