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

git lfs pushed files are empty #10665

Closed
2 of 7 tasks
markus-seidl opened this issue Mar 8, 2020 · 4 comments · Fixed by #10667
Closed
2 of 7 tasks

git lfs pushed files are empty #10665

markus-seidl opened this issue Mar 8, 2020 · 4 comments · Fixed by #10667

Comments

@markus-seidl
Copy link

Description

I try to push files from a client repository that has LFS enabled. LFS is enabled on the server and the push succeeds. Also the settings page of the repository lists the files as stored in the repository with their correct sizes.
However, on the next

  • clone
  • Zip download of the repository
  • Or direct download via web ui
    the files are empty or result in a 500 error. The 500 is, because the files are not there.

Screenshots

@markus-seidl
Copy link
Author

The solution is: The server didn't have access to the lfs directory and was swallowing the exception / warning / error.

I would suggest the exception about not being able to access the lfs directory should show up somewhere :)

@zeripath
Copy link
Contributor

zeripath commented Mar 8, 2020

I was about to say that your logs looked a bit sparse...

Looking at the code error should have been passed to the client at least - which is also incorrect because these errors might need sanitising.

Sigh I guess I'll have to go through and add logging to this.

@zeripath
Copy link
Contributor

zeripath commented Mar 8, 2020

Oh yeah I remember git-lfs may keep hitting the server if it gets a 500! So returning 500 for a permanent error will cause badness.

@markus-seidl
Copy link
Author

Thank you very much! @zeripath

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants