HTTP 500, when opening any commits from a certain repository

[keks24]

• Gitea version (or commit ref):

$ gitea --version
Gitea version 1.12.4 built with GNU Make 4.1, go1.14.8 : bindata, sqlite, sqlite_unlock_notify

• Git version:

$ git --version
git version 2.20.1

• Operating system:

$ uname --all
Linux gitea 5.4.60-1-pve #1 SMP PVE 5.4.60-2 (Fri, 04 Sep 2020 10:24:50 +0200) x86_64 GNU/Linux

$ < /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

• Database (use [x]):

  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite

• Can you reproduce the bug at https://try.gitea.io:

  • Yes (provide example URL)
  • No
  • Not relevant

• Log gist:
  gitea.log

Description

I am getting an HTTP 500 error, when I am trying to open any commit from my internal repository l4d2-configuration. The log file returns:

PANIC:: runtime error: slice bounds out of range

This also applies to a mirror repository on gitea.com.

For some reason it works on try.gitea.io and on codeberg.org; maybe because of some (custom) patches.

On github.com and gitlab.com the commit can be displayed as well, but these platforms cannot be used as reference actually.

I can reproduce this issue, when I recreate the repository on my internal server and do a git push --force.

Screenshots

[keks24]

This also relates to #12823

[zeripath]

Please do not open duplicate bug reports. Keeping on top of Gitea's issues is hard enough.
This is not only a duplicate of #12823 but is a duplicate of #12816 which was already fixed in master by the time it was reported.

[zeripath]

Fixed by #12771 and its backport #12776