Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
eNBeWe opened this issue Feb 16, 2022 · 3 comments · Fixed by #18784 or #18946
Closed

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

eNBeWe opened this issue Feb 16, 2022 · 3 comments · Fixed by #18784 or #18946
Labels
Milestone

Comments

@eNBeWe
Copy link

eNBeWe commented 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

@lunny
Copy link
Member

lunny commented Feb 16, 2022

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

@lunny lunny added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Feb 16, 2022
@eNBeWe
Copy link
Author

eNBeWe commented 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.

@lunny lunny added type/bug and removed issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail labels Feb 16, 2022
@lunny lunny added this to the 1.16.2 milestone Feb 16, 2022
zeripath pushed a commit that referenced this issue Feb 16, 2022
@parnic-sks
Copy link

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.

@lunny lunny reopened this Mar 1, 2022
@lunny lunny modified the milestones: 1.16.2, 1.16.3 Mar 1, 2022
zeripath pushed a commit that referenced this issue Mar 1, 2022
Chianina pushed a commit to Chianina/gitea that referenced this issue Mar 28, 2022
@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants