"parseRemoteUpdateOutput: unexpected update line" errors after upgrade to 1.20.3 #11626

Closed
opened 2025-11-02 09:42:51 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @pboguslawski on GitHub (Sep 11, 2023).

Originally assigned to: @lunny on GitHub.

Description

After upgrading 1.19.3 to 1.20.3 (both compiled from sources), gitea throws errors like...

2023/09/11 09:47:03 ...irror/mirror_pull.go:170:parseRemoteUpdateOutput() [W] parseRemoteUpdateOutput: unexpected update line " * [new ref] refs/pull/26997/head -> refs/pull/26997/head"
2023/09/11 09:47:03 ...irror/mirror_pull.go:170:parseRemoteUpdateOutput() [W] parseRemoteUpdateOutput: unexpected update line " * [new ref] refs/pull/26998/head -> refs/pull/26998/head"
2023/09/11 09:47:03 ...irror/mirror_pull.go:170:parseRemoteUpdateOutput() [W] parseRemoteUpdateOutput: unexpected update line " * [new ref] refs/pull/26998/merge -> refs/pull/26998/merge"
[...]
2023/09/11 09:47:15 .../indexer/stats/db.go:73:Index() [E] Unable to update language stats for ID 148c9c4b0500007d465156e4c2d7ff6873d23577 for default branch main in /path/to/repo/gitea.git. Error: Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
2023/09/11 09:47:15 ...dexer/stats/queue.go:24:handler() [E] stats queue indexer.Index(2) failed: Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction

...on mirror update. Gitea mirror sync at 09:47:03 looks like finished successfully in gitea's UI and no other problems found.

No such errors in 1.19.3 while syncing same mirrors.

Gitea Version

1.20.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.30.2

Operating System

Debian

How are you running Gitea?

Compiled from sources.

Database

MySQL/MariaDB

Originally created by @pboguslawski on GitHub (Sep 11, 2023). Originally assigned to: @lunny on GitHub. ### Description After upgrading 1.19.3 to 1.20.3 (both compiled from sources), gitea throws errors like... ``` 2023/09/11 09:47:03 ...irror/mirror_pull.go:170:parseRemoteUpdateOutput() [W] parseRemoteUpdateOutput: unexpected update line " * [new ref] refs/pull/26997/head -> refs/pull/26997/head" 2023/09/11 09:47:03 ...irror/mirror_pull.go:170:parseRemoteUpdateOutput() [W] parseRemoteUpdateOutput: unexpected update line " * [new ref] refs/pull/26998/head -> refs/pull/26998/head" 2023/09/11 09:47:03 ...irror/mirror_pull.go:170:parseRemoteUpdateOutput() [W] parseRemoteUpdateOutput: unexpected update line " * [new ref] refs/pull/26998/merge -> refs/pull/26998/merge" [...] 2023/09/11 09:47:15 .../indexer/stats/db.go:73:Index() [E] Unable to update language stats for ID 148c9c4b0500007d465156e4c2d7ff6873d23577 for default branch main in /path/to/repo/gitea.git. Error: Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction 2023/09/11 09:47:15 ...dexer/stats/queue.go:24:handler() [E] stats queue indexer.Index(2) failed: Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction ``` ...on mirror update. Gitea mirror sync at 09:47:03 looks like finished successfully in gitea's UI and no other problems found. No such errors in 1.19.3 while syncing same mirrors. ### Gitea Version 1.20.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.30.2 ### Operating System Debian ### How are you running Gitea? Compiled from sources. ### Database MySQL/MariaDB
GiteaMirror added the type/bug label 2025-11-02 09:42:51 -06:00
Author
Owner

@lunny commented on GitHub (Sep 11, 2023):

Pull heads should not be mirrored from remote.

@lunny commented on GitHub (Sep 11, 2023): Pull heads should not be mirrored from remote.
Author
Owner

@somera commented on GitHub (Nov 24, 2023):

Same with Gitea 1.21.0

@somera commented on GitHub (Nov 24, 2023): Same with Gitea 1.21.0
Author
Owner

@pboguslawski commented on GitHub (Dec 7, 2023):

Another type of error message from queue.go:

2023/12/07 18:26:50 ...dexer/stats/queue.go:24:handler() [E] stats queue indexer.Index(64) failed: Error 1062 (23000): Duplicate entry '64-Handlebars' for key 'UQE_language_stat_s'...
@pboguslawski commented on GitHub (Dec 7, 2023): Another type of error message from `queue.go`: ``` 2023/12/07 18:26:50 ...dexer/stats/queue.go:24:handler() [E] stats queue indexer.Index(64) failed: Error 1062 (23000): Duplicate entry '64-Handlebars' for key 'UQE_language_stat_s'... ```
Author
Owner

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

The problem comes from language_stat indexer but not parseRemoteUpdateOutput.

@lunny commented on GitHub (Mar 27, 2024): The problem comes from language_stat indexer but not `parseRemoteUpdateOutput`.
Author
Owner

@lifebarier commented on GitHub (Jul 24, 2025):

Was this ever addressed?
Getting same on "unexpected update line" 1.21.5

@lifebarier commented on GitHub (Jul 24, 2025): Was this ever addressed? Getting same on "unexpected update line" 1.21.5
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11626