github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Always need manual trigger "Sync missed branches from git data to databases" #12759

New Issue
Closed
opened 2025-11-02 10:20:04 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 10:20:04 -06:00
Owner
Copy Link

Originally created by @maxid on GitHub (Mar 29, 2024).

Description

Always need manual trigger "Sync missed branches from git data to databases" fixed create new branch missing

Gitea Version

1.21.4 ~1.21.8

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Always need manual trigger "Sync missed branches from git data to databases" fixed create new branch missing###

Git Version

2.40.1

Operating System

centos 7

How are you running Gitea?

Gitea Version

1.21.8 built with GNU Make 4.4.1, go1.21.8 : bindata, timetzdata, sqlite, sqlite_unlock_notify

Git Version

2.40.1, Wire Protocol Version 2 Enabled

Repo Count

265

System Status
Current Goroutines 69
Current Memory Usage 82 MiB
Total Memory Allocated 98 GiB
Memory Obtained 238 MiB
Pointer Lookup Times 0
Memory Allocations 2204340482
Memory Frees 2203820486
Current Heap Usage 82 MiB
Heap Memory Obtained 214 MiB
Heap Memory Idle 108 MiB
Heap Memory In Use 106 MiB
Heap Memory Released 75 MiB
Heap Objects 519996
Bootstrap Stack Usage 2.4 MiB
Stack Memory Obtained 2.4 MiB
MSpan Structures Usage 1.3 MiB
MSpan Structures Obtained 2.6 MiB
MCache Structures Usage 4.7 KiB
MCache Structures Obtained 15 KiB
Profiling Bucket Hash Table Obtained 8.1 MiB
GC Metadata Obtained 10 MiB
Other System Allocation Obtained 1.1 MiB
Next GC Recycle 159 MiB
Since Last GC Time 69.4s
Total GC Pause 1.5s
Last GC Pause 0.000s
GC Times 9505

Database

SQLite

Originally created by @maxid on GitHub (Mar 29, 2024). ### Description Always need manual trigger "Sync missed branches from git data to databases" fixed create new branch missing ### Gitea Version 1.21.4 ~1.21.8 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots Always need manual trigger "Sync missed branches from git data to databases" fixed create new branch missing### ### Git Version 2.40.1 ### Operating System centos 7 ### How are you running Gitea? ### Gitea Version 1.21.8 built with GNU Make 4.4.1, go1.21.8 : bindata, timetzdata, sqlite, sqlite_unlock_notify ### Git Version 2.40.1, Wire Protocol Version 2 Enabled ### Repo Count 265 ### System Status ||| | ---- | ----| |Current Goroutines|69| Current Memory Usage|82 MiB Total Memory Allocated|98 GiB Memory Obtained|238 MiB Pointer Lookup Times|0 Memory Allocations|2204340482 Memory Frees|2203820486 Current Heap Usage|82 MiB Heap Memory Obtained|214 MiB Heap Memory Idle|108 MiB Heap Memory In Use|106 MiB Heap Memory Released|75 MiB Heap Objects|519996 Bootstrap Stack Usage|2.4 MiB Stack Memory Obtained|2.4 MiB MSpan Structures Usage|1.3 MiB MSpan Structures Obtained|2.6 MiB MCache Structures Usage|4.7 KiB MCache Structures Obtained|15 KiB Profiling Bucket Hash Table Obtained|8.1 MiB GC Metadata Obtained|10 MiB Other System Allocation Obtained|1.1 MiB Next GC Recycle|159 MiB Since Last GC Time|69.4s Total GC Pause|1.5s Last GC Pause|0.000s GC Times|9505 ### Database SQLite
GiteaMirror added the type/bug label 2025-11-02 10:20:04 -06:00
GiteaMirror commented 2025-11-02 10:20:06 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 29, 2024):

Please run Sync hooks task on admin panel first.

@lunny commented on GitHub (Mar 29, 2024): Please run `Sync hooks` task on admin panel first.
GiteaMirror commented 2025-11-02 10:20:06 -06:00
Author
Owner
Copy Link

@maxid commented on GitHub (Apr 1, 2024):

not work

@maxid commented on GitHub (Apr 1, 2024): not work
GiteaMirror commented 2025-11-02 10:20:06 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 1, 2024):

Can you find more logs or run gitea doctor to get some results?

@lunny commented on GitHub (Apr 1, 2024): Can you find more logs or run gitea doctor to get some results?
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#12759
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?