mirror of
https://github.com/go-gitea/gitea.git
synced 2026-03-12 02:24:21 -05:00
LFS: unexpected EOF despite good integrity of the file on the server #2452
Closed
opened 2025-11-02 04:36:45 -06:00 by GiteaMirror
·
10 comments
No Branch/Tag Specified
main
release/v1.25
release/v1.24
release/v1.23
release/v1.22
release/v1.21
release/v1.20
release/v1.19
release/v1.18
release/v1.17
release/v1.16
release/v1.15
release/v1.14
release/v1.13
release/v1.12
release/v1.11
release/v1.10
release/v1.9
release/v1.8
v1.25.3
v1.25.2
v1.25.1
v1.25.0
v1.24.7
v1.25.0-rc0
v1.26.0-dev
v1.24.6
v1.24.5
v1.24.4
v1.24.3
v1.24.2
v1.24.1
v1.24.0
v1.23.8
v1.24.0-rc0
v1.25.0-dev
v1.23.7
v1.23.6
v1.23.5
v1.23.4
v1.23.3
v1.23.2
v1.23.1
v1.23.0
v1.23.0-rc0
v1.24.0-dev
v1.22.6
v1.22.5
v1.22.4
v1.22.3
v1.22.2
v1.22.1
v1.22.0
v1.23.0-dev
v1.22.0-rc1
v1.21.11
v1.22.0-rc0
v1.21.10
v1.21.9
v1.21.8
v1.21.7
v1.21.6
v1.21.5
v1.21.4
v1.21.3
v1.21.2
v1.20.6
v1.21.1
v1.21.0
v1.21.0-rc2
v1.21.0-rc1
v1.20.5
v1.22.0-dev
v1.21.0-rc0
v1.20.4
v1.20.3
v1.20.2
v1.20.1
v1.20.0
v1.19.4
v1.21.0-dev
v1.20.0-rc2
v1.20.0-rc1
v1.20.0-rc0
v1.19.3
v1.19.2
v1.19.1
v1.19.0
v1.19.0-rc1
v1.20.0-dev
v1.19.0-rc0
v1.18.5
v1.18.4
v1.18.3
v1.18.2
v1.18.1
v1.18.0
v1.17.4
v1.18.0-rc1
v1.19.0-dev
v1.18.0-rc0
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.17.0-rc2
v1.16.9
v1.17.0-rc1
v1.18.0-dev
v1.16.8
v1.16.7
v1.16.6
v1.16.5
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
v1.15.11
v1.17.0-dev
v1.16.0-rc1
v1.15.10
v1.15.9
v1.15.8
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.14.7
v1.15.0
v1.15.0-rc3
v1.14.6
v1.15.0-rc2
v1.14.5
v1.16.0-dev
v1.15.0-rc1
v1.14.4
v1.14.3
v1.14.2
v1.14.1
v1.14.0
v1.13.7
v1.14.0-rc2
v1.13.6
v1.13.5
v1.14.0-rc1
v1.15.0-dev
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.6
v1.13.0-rc2
v1.14.0-dev
v1.13.0-rc1
v1.12.5
v1.12.4
v1.12.3
v1.12.2
v1.12.1
v1.11.8
v1.12.0
v1.11.7
v1.12.0-rc2
v1.11.6
v1.12.0-rc1
v1.13.0-dev
v1.11.5
v1.11.4
v1.11.3
v1.10.6
v1.12.0-dev
v1.11.2
v1.10.5
v1.11.1
v1.10.4
v1.11.0
v1.11.0-rc2
v1.10.3
v1.11.0-rc1
v1.10.2
v1.10.1
v1.10.0
v1.9.6
v1.9.5
v1.10.0-rc2
v1.11.0-dev
v1.10.0-rc1
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
v1.9.0-rc2
v1.10.0-dev
v1.9.0-rc1
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.8.0-rc3
v1.7.6
v1.8.0-rc2
v1.7.5
v1.8.0-rc1
v1.9.0-dev
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.7.0-rc3
v1.6.4
v1.7.0-rc2
v1.6.3
v1.7.0-rc1
v1.7.0-dev
v1.6.2
v1.6.1
v1.6.0
v1.6.0-rc2
v1.5.3
v1.6.0-rc1
v1.6.0-dev
v1.5.2
v1.5.1
v1.5.0
v1.5.0-rc2
v1.5.0-rc1
v1.5.0-dev
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.4.0-rc3
v1.4.0-rc2
v1.3.3
v1.4.0-rc1
v1.3.2
v1.3.1
v1.3.0
v1.3.0-rc2
v1.3.0-rc1
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.2.0-rc3
v1.2.0-rc2
v1.1.4
v1.2.0-rc1
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.99
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
Mirrored from GitHub Pull Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/gitea#2452
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @qzmfranklin on GitHub (Oct 25, 2018).
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
logito 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 clonefrom 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.oidof the lfs file to locate the file.scpto 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.
@zeripath commented on GitHub (Oct 25, 2018):
hmm... looking at your logs I see:
/Users/ttaylorr/go/src/github.com/git-lfs/git-lfs/errors/types.go:188. Are you running Gitea on a Mac?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.
@qzmfranklin commented on GitHub (Oct 26, 2018):
Gitea was running on a Ubuntu 18.04.1 server.
This issue happens for only a few files. I tried
--skip-smudgeand verified the content of the lfs object file. The file has exactly the same content as it should (verified byxxdanddiff).To get around this issue, I have removed those faulting files. Running out of ideas to try.
@zeripath commented on GitHub (Oct 27, 2018):
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.
@stale[bot] commented on GitHub (Jan 5, 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.
@ghost commented on GitHub (Jan 7, 2019):
I have the exact same issue. This is related to gzip.
When I disable
ENABLE_GZIPin the config and the issue will be solved.But when I enable the
ENABLE_GZIPoption, I won't be able to download some files via git-lfs or web (ERR_CONTENT_LENGTH_MISMATCH)Similar issue: #4853
@qzmfranklin commented on GitHub (Jan 8, 2019):
@yasuokav : Thanks for confirming and providing a workaround. This is infinitely helpful to us.
@zeripath commented on GitHub (Jan 8, 2019):
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.
@ghost commented on GitHub (Jan 8, 2019):
@zeripath
1.zip
SHA1(1.png)= b9a88e4d43568845689750acbec93de346dbc8a4
Size: 39,683 bytes
Maybe Gitea sent the content-length of original file size but it's a gzipped response. Is this the problem?
Gitea(Gzip enabled):
Apache(Gzip enabled):
@zeripath commented on GitHub (Jan 8, 2019):
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.
@zeripath commented on GitHub (Jan 8, 2019):
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.