Internal Server Error when listing locks or accessing locked files in web view #8569

New Issue

GiteaMirror · 2025-11-02T08:11:04-06:00

GiteaMirror commented

2025-11-02 08:11:04 -06:00

Originally created by @eNBeWe on GitHub (Feb 16, 2022).

Gitea Version

1.16.1

Git Version

2.25.1

Operating System

Linux (Ubuntu Server 20.04.3)

How are you running Gitea?

Binary installation very similar to instructions from the docs.
Service is run through systemd.

Database

SQLite

Can you reproduce the bug on the Gitea demo site?

No (since LFS is not available there)

Log Gist

No response

Description

I have a repository with a few locked files (xlsx).
As soon as I try to access the file through the web interface, I receive a HTTP 500 Internal Server Error. I can download the the file when I use the "/raw"-Url.
When I try to show the locked files in the repository from the settings, I also get a HTTP 500.

I tried to reproduce the issue on another server running Gitea 1.15.6 and the issue didn't occur. I will try to update the server and see if it breaks.

Screenshots

No response

Originally created by @eNBeWe on GitHub (Feb 16, 2022). ### Gitea Version 1.16.1 ### Git Version 2.25.1 ### Operating System Linux (Ubuntu Server 20.04.3) ### How are you running Gitea? Binary installation very similar to instructions from the docs. Service is run through systemd. ### Database SQLite ### Can you reproduce the bug on the Gitea demo site? No (since LFS is not available there) ### Log Gist _No response_ ### Description I have a repository with a few locked files (xlsx). As soon as I try to access the file through the web interface, I receive a HTTP 500 Internal Server Error. I can download the the file when I use the "/raw"-Url. When I try to show the locked files in the repository from the settings, I also get a HTTP 500. I tried to reproduce the issue on another server running Gitea 1.15.6 and the issue didn't occur. I will try to update the server and see if it breaks. ### Screenshots _No response_

GiteaMirror added the type/bug label 2025-11-02 08:11:04 -06:00

GiteaMirror closed this issue

2025-11-02 08:11:04 -06:00

GiteaMirror commented

2025-11-02 08:11:05 -06:00

@lunny commented on GitHub (Feb 16, 2022):

What's locked files? Did you mean git LFS Lock?

@lunny commented on GitHub (Feb 16, 2022): What's locked files? Did you mean git LFS Lock?

GiteaMirror commented

2025-11-02 08:11:05 -06:00

@eNBeWe commented on GitHub (Feb 16, 2022):

Yes, sort of. The files are marked as lockable by GIT LFS, but the actual files are not tracked by LFS.
So the entry in the .gitattributes is just
*.data lockable

You can look at the (working) version of my test repository at https://git.enbewe.de/Stuff/InternalErrorOnLocks
The server is running 1.15.6 (as you can see) and you can access the page https://git.enbewe.de/Stuff/InternalErrorOnLocks/src/branch/master/data/File1.data just fine.
I have the same repository on another Gitea server (not publicly accessible) where it breaks.

@eNBeWe commented on GitHub (Feb 16, 2022): Yes, sort of. The files are marked as lockable by GIT LFS, but the actual files are not tracked by LFS. So the entry in the .gitattributes is just `*.data lockable` You can look at the (working) version of my test repository at https://git.enbewe.de/Stuff/InternalErrorOnLocks The server is running 1.15.6 (as you can see) and you can access the page https://git.enbewe.de/Stuff/InternalErrorOnLocks/src/branch/master/data/File1.data just fine. I have the same repository on another Gitea server (not publicly accessible) where it breaks.

GiteaMirror commented

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

@parnic-sks commented on GitHub (Feb 28, 2022):

We are seeing this part of the reported issue:

As soon as I try to access the file through the web interface, I receive a HTTP 500 Internal Server Error.

fixed in 1.16.2. However, this part:

When I try to show the locked files in the repository from the settings, I also get a HTTP 500.

is still a problem.

@parnic-sks commented on GitHub (Feb 28, 2022): We are seeing this part of the reported issue: > As soon as I try to access the file through the web interface, I receive a HTTP 500 Internal Server Error. fixed in 1.16.2. However, this part: > When I try to show the locked files in the repository from the settings, I also get a HTTP 500. is still a problem.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#8569