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

gitea git clone failed when using ENABLE_GZIP for tar.gz file. #4853

Closed
simonwu-os opened this issue Sep 3, 2018 · 1 comment · Fixed by #5722
Closed

gitea git clone failed when using ENABLE_GZIP for tar.gz file. #4853

simonwu-os opened this issue Sep 3, 2018 · 1 comment · Fixed by #5722
Labels
Milestone

Comments

@simonwu-os
Copy link

Dear all,
I use gitea using git lfs track '*.tar.gz'. I upload an tar file (downloaded from https://codeload.github.com/masterzen/nginx-upload-progress-module/tar.gz/v0.9.2). Its sha256 checksum is 'b286689355442657650421d8e8398bd4abf9dbbaade65947bb0cb74a349cc497'.
The lfs file stored in the server is correctly. Its checksum is the same. But when ENABLE_GZIP is true,
git clone the repo , it failed.
The terminal display:
Downloading nginx-upload-progress-module-0.9.2.tar.gz (17 KB)
Error downloading object: nginx-upload-progress-module-0.9.2.tar.gz (b286689): Smudge error: Error downloading nginx-upload-progress-module-0.9.2.tar.gz (b286689355442657650421d8e8398bd4abf9dbbaade65947bb0cb74a349cc497): cannot write data to tempfile "/works/gitworks/2018-develop/zdd/testout/out/test-repo/.git/lfs/incomplete/b286689355442657650421d8e8398bd4abf9dbbaade65947bb0cb74a349cc497.tmp": LFS: unexpected EOF

When I change ENABLE_GZIP to false, and restart gitea, it works for git clone.

So I think git lfs upload is correct. The problem is ENABLE_GZIP, when it's true, git clone don't works for the tar.gz file.
ps: we can git clone for other lfs files(such as we compile lib files. when ENABLE_GZIP is true) .

@stale
Copy link

stale bot commented Jan 11, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Jan 11, 2019
@lafriks lafriks added this to the 1.8.0 milestone Jan 23, 2019
@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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants