Whenever anybody talks about "the community" as if they were not part of it, and pretend that the responsibility for a certain fix they desire so much lies not with them, but with others, all too often words like "crazy" are used with the obvious goal of shaming others into working on the fix. I have to admit that I am somewhat allergic to statements like these. Enough work to keep several contributors busy for quite a while. This proposed fix will need a ton of work to get over the finish line. It is a bit crazy that this has not been prioritized by community.īeta Was this translation helpful? Give feedback. The problem is in git client, both in crc32 (checksum) and in many of the file io functions (see branch). The issue is related to c/c++ long type is 32bit on Windows (independent of CPU architecture) - while on 64bit linux it is 64bit.Ī fix was proposed 2 years ago ( branch: size_t6). I can see the mass confusion among our dev / test / compliance when they check out a game, and files are there, but not the actual files. A normal git pull will fetch the "reference files" so folder look all good but files are just xml references to the lfs repo. will not perform a git lfs pull automatically. We have confirmed that using git lfs directly works all good, and with smudge and filter skip all is good.Īlthough a ok work-around for now, third-party tools like embedded git clients (visual code, visual studio, gitkraken etc). 👀 Was this translation helpful? Give feedback. **So, big question, what am I missing? Why was I allowed to work on a 5GB file ** 😃ĭoes it mean the 4GB file limit doesn't apply all the time? Is there a way I can reproduce the issue with certainty?
#GIT LFS WINDOWS ZIP FILE#
Zip file is NOT corrupted, and there were NO errors.To proceed further I even did a checkout of a fresh branch, pushed some changes.Confirmed through Git status that the file exists.Created a new repository in a Test GitHub Enterprise Instance, cloned the same and executed the following commands in order.Zipped the above file - so that I can check file corruption.Added some Jupyter Python Extensions for Visual Studio Code.Configured the VM with the following all latest as of date i.e.
#GIT LFS WINDOWS WINDOWS 10#
0 kommentar(er)
