github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-10 13:56:06 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

cron.update_mirrors updates only 51 mirrors in one run #8615

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

Originally created by @somera on GitHub (Feb 25, 2022).

Gitea Version

1.16.2

Git Version

2.25.1

Operating System

Ubuntu 20.04.4

How are you running Gitea?

Precompiled gitea-1.16.2-linux-amd64

Database

PostgreSQL

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

In #18607 I reported problem with the ron.update_mirrors. Now it's wioking, but the cron is updating only 51 mirrors.

Status after Gitea update

image

Status after the first run Gitea updates 51 mirrors.

image

why only 51?

Status after the second run Gitea updates 51 mirrors.

image

why only 51?

51 is same like some days ago: https://github.com/go-gitea/gitea/issues/18607#issuecomment-1044120194

This

[mirror]
; Default interval as a duration between each check
DEFAULT_INTERVAL = 8h
; Min interval as a duration must be > 1m
MIN_INTERVAL = 10m
LENGTH = 20000
TYPE = level

[queue.mirror]
LENGTH = 20000
WORKERS = 1

[cron.update_mirrors]
; Every hour
SCHEDULE = 0 0 * * * *
PULL_LIMITS = 1000
PUSH_LIMITS = 1000

is my current configuration.

With

PULL_LIMITS = 1000

gitea should update 1000 mirrors in one run. Right?

After 4th run I did this:

  • flush-queues
  • stop gitea
  • remove ./../data/queues/common folder
  • start gitea

And the 5th run updated again only 51 mirrors.

How can I update in Gitea 1.16.x 1000, 2000 or more mirrors in one row? And not only 51.

My current "solution" is: run the cron every hour and update the 51 mirror on every run. In my case it needs 179 runs.

Originally created by @somera on GitHub (Feb 25, 2022). ### Gitea Version 1.16.2 ### Git Version 2.25.1 ### Operating System Ubuntu 20.04.4 ### How are you running Gitea? Precompiled [gitea-1.16.2-linux-amd64](https://github.com/go-gitea/gitea/releases/download/v1.16.2/gitea-1.16.2-linux-amd64) ### Database PostgreSQL ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Description In #18607 I reported problem with the ron.update_mirrors. Now it's wioking, but the cron is updating only 51 mirrors. Status after Gitea update ![image](https://user-images.githubusercontent.com/8334250/155601563-caf1de4f-034a-4e2a-9bc9-7b385a62f075.png) Status after the first run Gitea updates 51 mirrors. ![image](https://user-images.githubusercontent.com/8334250/155601647-be7afc27-ed0f-4049-89a9-df0f2a22fdde.png) why only 51? Status after the second run Gitea updates 51 mirrors. ![image](https://user-images.githubusercontent.com/8334250/155601695-6839d25d-93b6-4445-9343-f62f7c4979e5.png) why only 51? 51 is same like some days ago: https://github.com/go-gitea/gitea/issues/18607#issuecomment-1044120194 This ``` [mirror] ; Default interval as a duration between each check DEFAULT_INTERVAL = 8h ; Min interval as a duration must be > 1m MIN_INTERVAL = 10m LENGTH = 20000 TYPE = level [queue.mirror] LENGTH = 20000 WORKERS = 1 [cron.update_mirrors] ; Every hour SCHEDULE = 0 0 * * * * PULL_LIMITS = 1000 PUSH_LIMITS = 1000 ``` is my current configuration. With `PULL_LIMITS = 1000` gitea should update 1000 mirrors in one run. Right? After 4th run I did this: - flush-queues - stop gitea - remove ./../data/queues/common folder - start gitea And the 5th run updated again only 51 mirrors. How can I update in Gitea 1.16.x 1000, 2000 or more mirrors in one row? And not only 51. My current "solution" is: run the cron every hour and update the 51 mirror on every run. In my case it needs 179 runs.
GiteaMirror added the issue/not-a-bug label 2025-11-02 08:12:29 -06:00
GiteaMirror commented 2025-11-02 08:12:31 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 28, 2022):

@somera Please read the configuration cheat sheet.

https://docs.gitea.io/en-us/config-cheat-sheet/#cron---update-mirrors-cronupdate_mirrors

[cron.update_mirrors]
PULL_LIMIT = 1000
PUSH_LIMIT = 1000
@zeripath commented on GitHub (Feb 28, 2022): @somera Please read the configuration cheat sheet. https://docs.gitea.io/en-us/config-cheat-sheet/#cron---update-mirrors-cronupdate_mirrors ``` [cron.update_mirrors] PULL_LIMIT = 1000 PUSH_LIMIT = 1000 ```
GiteaMirror commented 2025-11-02 08:12:31 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Feb 28, 2022):

@somera Please read the configuration cheat sheet.

https://docs.gitea.io/en-us/config-cheat-sheet/#cron---update-mirrors-cronupdate_mirrors

[cron.update_mirrors]
PULL_LIMIT = 1000
PUSH_LIMIT = 1000

My mistake. I need glasses.

@somera commented on GitHub (Feb 28, 2022): > @somera Please read the configuration cheat sheet. > > https://docs.gitea.io/en-us/config-cheat-sheet/#cron---update-mirrors-cronupdate_mirrors > > ``` > [cron.update_mirrors] > PULL_LIMIT = 1000 > PUSH_LIMIT = 1000 > ``` My mistake. I need glasses.
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 issue/not-a-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#8615
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?