-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
LFS: unexpected EOF despite good integrity of the file on the server #5182
Comments
hmm... looking at your logs I see: I wonder if the file that's being downloaded to be smudged by git-lfs has the wrong line-endings?
should allow you to skip the smudge action and interrogate the smudge files to check how they are formatted - although they might actually already be in your checkout for you to take a look at. |
Gitea was running on a Ubuntu 18.04.1 server. This issue happens for only a few files. I tried To get around this issue, I have removed those faulting files. Running out of ideas to try. |
Are the faulting files proprietary? Would it be possible to post them so I could try them. Things that come to mind are:
The problem could be anywhere, but it's unlikely to be on your client end if you say it works for other providers. However it might be good to try a different client machine to see if it's restricted to a single client. |
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. |
I have the exact same issue. This is related to gzip. Similar issue: #4853 |
@yasuokav : Thanks for confirming and providing a workaround. This is infinitely helpful to us. |
An example file would really help in debugging this. If the problem files are all the same length that would also help identify this. I am concerned that this implies there is either a buffer overflow or underrun here - those tend to be exploitable, so it would be helpful to get this identified. I guess we need to look at where gzip is enabled and see if there's an problem there. |
@zeripath Gitea(Gzip enabled):
Apache(Gzip enabled):
|
Ah ok. That makes things interesting. It appears that gziper.Gziper is supposed to reset the content-length. I wonder if the lfs.getContentHandler is somehow overriding this. |
Certainly the range header code will not work in a gzip environment so even if this isn't relevant to the bug you're noticing it's definitely something. |
git-lfs/2.5.2
git version 2.17.1
Ubuntu 18.04.1
[x]
):Description
I have a local gitea server set up at host http://git.corp.logiocean.com:3000.
I pushed an LFS-enabled repo, named
logi
to the gitea server. Everything worked fine until I triedgit clone
, which produced the above described error.I pushed the same repo (at the same commit) to github and
git clone
from github, everything worked.I have verified that the git commit hash on github and on my local gitea server are exactly the same.
I have also verified that the LFS file that failed to download are intact on the server. Here is how I verified it:
/home/git/data/lfs
.oid
of the lfs file to locate the file.scp
to copy the file in question to my own desktop and verified (using diff and other tools) that the size of the file and the content of the file are indeed intact.I have searched for similar issues across this repo and in many other places. Have not found one with exactly the same syndrome.
Posting to hopefully help others who are having the same problem.
Any help would be much appreciated! Thanks in advance.
The text was updated successfully, but these errors were encountered: