Skip to content

Creating repo with one empty commit causes repository page to fail #16668

Closed
@jotoho

Description

@jotoho
  • Gitea version (or commit ref): 1.15.0+rc2 (deployed via docker)
  • Git version: 2.30.2 in server container; 2.32.0 on client PC
  • Operating system:
    • Docker container created from slightly outdated official image downloaded from Docker Hub (container is a few days old)
    • Host is Raspberry Pi 4 with 4GB RAM running the official 64-bit Raspberry Pi OS
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io: (account activation link has yet to be delivered to my mailbox. Will test once I can create repos there.)
    • Yes (provide example URL)
    • No
  • Log gist: https://gist.github.com/jotoho/25b55e1c1c0a66202cb282822d79921e

Description

Creating an empty repository with the following commands:

git init
git commit --allow-empty -m "Initial commit"

and then pushing it to a new repository on gitea causes attempts to open the repo in the webinterface to fail with an "Internal Server Error" message. Creating and pushing a second commit with actual files causes the Webinterface to behave normally again.

For transparency: The gitea instance is running behind a HTTPS reverse proxy (Caddy) but I cannot imagine that having anything to do with this issue.

Screenshots

Screenshot_20210811_191750

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions