Mirror update interval corrupted - changed 8H -> 318538h39m30.304065536s #1067

New Issue

GiteaMirror · 2025-11-02T03:47:07-06:00

GiteaMirror commented

2025-11-02 03:47:07 -06:00

Originally created by @issmirnov on GitHub (Sep 15, 2017).

Gitea version (or commit ref): 1.2.0+rc2
Git version: 2.7.4
Operating system: Ubuntu 16.04 LTS
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Description

After upgrading to the latest gitea, none of my mirrors are working.

Checking myapp.ini, things look okay:

[cron]
ENABLED      = true
RUN_AT_START = true

; Update mirrors
[cron.update_mirrors]
SCHEDULE = @every 10m

But, when I open a repo, I see:

Mirror interval (valid time units are "h", "m", "s") = 318538h39m30.304065536s

I did not change this. It used to be 8h intervals. I think the latest version somehow corrupted this value.

Screenshots

Mirror: http://cloud.ivansmirnov.name/2O3N2u0s3y2t

Originally created by @issmirnov on GitHub (Sep 15, 2017). - Gitea version (or commit ref): 1.2.0+rc2 - Git version: 2.7.4 - Operating system: Ubuntu 16.04 LTS - Database (use `[x]`): - [ ] PostgreSQL - [X] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant ## Description After upgrading to the latest gitea, none of my mirrors are working. Checking my`app.ini`, things look okay: ``` [cron] ENABLED = true RUN_AT_START = true ; Update mirrors [cron.update_mirrors] SCHEDULE = @every 10m ``` But, when I open a repo, I see: ``` Mirror interval (valid time units are "h", "m", "s") = 318538h39m30.304065536s ``` I did not change this. It used to be 8h intervals. I think the latest version somehow corrupted this value. ## Screenshots 1. Mirror: http://cloud.ivansmirnov.name/2O3N2u0s3y2t

GiteaMirror added the type/bug label 2025-11-02 03:47:07 -06:00

GiteaMirror closed this issue

2025-11-02 03:47:07 -06:00

GiteaMirror commented

2025-11-02 03:47:08 -06:00

@cez81 commented on GitHub (Sep 15, 2017):

Do you remember what version you upgraded from?

@cez81 commented on GitHub (Sep 15, 2017): Do you remember what version you upgraded from?

GiteaMirror commented

2025-11-02 03:47:08 -06:00

@issmirnov commented on GitHub (Sep 15, 2017):

Yes, v1.1.4

Upgraded by downloading new binary, replacing the old one, and restarting tye systemd service.

@issmirnov commented on GitHub (Sep 15, 2017): Yes, [v1.1.4](https://github.com/go-gitea/gitea/releases/tag/v1.1.4) Upgraded by downloading new binary, replacing the old one, and restarting tye systemd service.

GiteaMirror commented

2025-11-02 03:47:08 -06:00

@cez81 commented on GitHub (Oct 17, 2017):

I've tried reproducing this bug using 1.1.4 and upgrading to 1.2.1 without success. Migration code hasn't changed between 1.2.0-rc2 and 1.2.1. If you still happen to have the log from the upgrade that would be interesting to see.
The migration was broken at one point but that was fixed back in April.

@cez81 commented on GitHub (Oct 17, 2017): I've tried reproducing this bug using 1.1.4 and upgrading to 1.2.1 without success. Migration code hasn't changed between 1.2.0-rc2 and 1.2.1. If you still happen to have the log from the upgrade that would be interesting to see. The migration was broken at one point but that was fixed back in April.

GiteaMirror commented

2025-11-02 03:47:08 -06:00

@issmirnov commented on GitHub (Oct 28, 2017):

This has come back. I upgraded from 1.2.1 to 1.2.2. Mirror interval set to 318538h39m30.304065536s again.

@issmirnov commented on GitHub (Oct 28, 2017): This has come back. I upgraded from 1.2.1 to 1.2.2. Mirror interval set to 318538h39m30.304065536s again.

GiteaMirror commented

2025-11-02 03:47:08 -06:00

@lafriks commented on GitHub (Oct 28, 2017):

There was no migrations at all between 1.2.1 and 1.2.2

@lafriks commented on GitHub (Oct 28, 2017): There was no migrations at all between 1.2.1 and 1.2.2

GiteaMirror commented

2025-11-02 03:47:09 -06:00

@issmirnov commented on GitHub (Nov 3, 2017):

Odd. I'll close for now, will reopen if the same repos get corrupted sync times again.

@issmirnov commented on GitHub (Nov 3, 2017): Odd. I'll close for now, will reopen if the same repos get corrupted sync times again.

GiteaMirror referenced this issue

2025-11-02 11:53:39 -06:00