You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just tried to upgrade my Gitea server, but it kept on crashing with the above error message. I found that this appeared some time between 1.2.0rc2 and 1.2.0rc3, and I traced it to that specific commit.
I followed the code path to this error, and created the following Bash line to find which of my repositories was causing the issue:
and it turns out that a copy of the Quagga repository was causing the issue:
andrew/quagga.git
=======
tagger Denis Ovsienko <infrastation@yandex.ru> 1317300784 +0400
tagger Denis Ovsienko <infrastation@yandex.ru> 1325771815 +0400
tagger paul <paul>
tagger paul <paul>
tagger Chris Hall (GMCH) <chris.hall@highwayman.com> 1305620650 +0100
tagger Chris Hall (GMCH) <chris.hall@highwayman.com> 1305620770 +0100
tagger Chris Hall (GMCH) <chris.hall@highwayman.com> 1305620808 +0100
tagger Chris Hall (GMCH) <chris.hall@highwayman.com> 1305621324 +0100
tagger Chris Hall (GMCH) <chris.hall@highwayman.com> 1305621440 +0100
tagger Chris Hall (GMCH) <chris.hall@highwayman.com> 1305621066 +0100
tagger Chris Hall (GMCH) <chris.hall@highwayman.com> 1305620973 +0100
tagger Chris Hall (GMCH) <chris.hall@highwayman.com> 1305621511 +0100
tagger Chris Hall (GMCH) <chris.hall@highwayman.com> 1305621602 +0100
tagger Chris Hall <chris.hall@highwayman.com> 1315351914 +0100
tagger Chris Hall <chris.hall@highwayman.com> 1315349362 +0100
tagger Chris Hall (GMCH) <chris.hall@highwayman.com> 1332158374 +0000
tagger Chris Hall <chris.hall@highwayman.com> 1332504450 +0000
tagger Chris Hall <chris.hall@highwayman.com> 1332505242 +0000
tagger Chris Hall <chris.hall@highwayman.com> 1336384768 +0100
tagger Chris Hall <chris.hall@highwayman.com> 1339165556 +0100
tagger Paul Jakma <paul@clubi.ie> 1131254104 +0000
tagger Paul Jakma <paul@quagga.net> 1143735361 +0100
tagger Paul Jakma <paul@quagga.net> 1143805065 +0100
tagger Paul Jakma <paul@quagga.net> 1143805186 +0100
tagger Paul Jakma <paul@quagga.net> 1147109393 +0100
tagger gdt <gdt>
tagger jardin <jardin>
tagger gdt <gdt>
tagger gdt <gdt>
tagger paul <paul>
tagger paul <paul>
tagger hasso <hasso>
tagger paul <paul>
tagger ajs <ajs>
tagger ajs <ajs>
tagger ajs <ajs>
tagger ajs <ajs>
tagger paul <paul>
[...]
For now, I've deleted the repository so the Gitea upgrade can proceed, but I think this code (https://github.com/go-gitea/gitea/blob/master/vendor/code.gitea.io/git/signature.go#L35) should be able to deal with a missing timestamp, especially since there are repositories out in the wild that have tags with author lines that are missing timestamps.
The text was updated successfully, but these errors were encountered:
Description
I just tried to upgrade my Gitea server, but it kept on crashing with the above error message. I found that this appeared some time between 1.2.0rc2 and 1.2.0rc3, and I traced it to that specific commit.
I followed the code path to this error, and created the following Bash line to find which of my repositories was causing the issue:
and it turns out that a copy of the Quagga repository was causing the issue:
GitHub seems to deal with one of these tags somewhat more gracefully: https://github.com/Quagga/quagga/releases/tag/zebra_org_20030428
For now, I've deleted the repository so the Gitea upgrade can proceed, but I think this code (https://github.com/go-gitea/gitea/blob/master/vendor/code.gitea.io/git/signature.go#L35) should be able to deal with a missing timestamp, especially since there are repositories out in the wild that have tags with author lines that are missing timestamps.
The text was updated successfully, but these errors were encountered: