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

Abnormal synced commits and new reference records #14272

New Issue
Open
opened 2025-11-02 11:08:12 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 11:08:12 -06:00
Owner
Copy Link

Originally created by @imkuang on GitHub (Mar 19, 2025).

Description

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

Image

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

Originally created by @imkuang on GitHub (Mar 19, 2025). ### Description Recently I observed some sync records on my Gitea instance as follows: ![Image](https://github.com/user-attachments/assets/b9d2628e-8e6c-43df-ba68-b52a826e4587) 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
GiteaMirror added the type/bug label 2025-11-02 11:08:12 -06:00
GiteaMirror commented 2025-11-02 11:08:13 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Mar 19, 2025):

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

@wxiaoguang commented on GitHub (Mar 19, 2025): IIRC not only one issue mentions that there are too many "mirror" activity records.
GiteaMirror commented 2025-11-02 11:08:13 -06:00
Author
Owner
Copy Link

@imkuang commented on GitHub (Mar 19, 2025):

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 commented on GitHub (Mar 19, 2025): 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?
GiteaMirror commented 2025-11-02 11:08:14 -06:00
Author
Owner
Copy Link

@imkuang commented on GitHub (Mar 19, 2025):

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: https://github.com/go-gitea/gitea/issues/27961

@imkuang commented on GitHub (Mar 19, 2025): > 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: https://github.com/go-gitea/gitea/issues/27961
GiteaMirror commented 2025-11-02 11:08:14 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 19, 2025):

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

@lunny commented on GitHub (Mar 19, 2025): There refs are wired. Have you mirrored from https://gitea.com/gitea/act_runner ?
GiteaMirror commented 2025-11-02 11:08:14 -06:00
Author
Owner
Copy Link

@imkuang commented on GitHub (Mar 19, 2025):

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

@imkuang commented on GitHub (Mar 19, 2025): > 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
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 type/bug
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#14272
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?