{"thread":{"id":"57872","subject":"Git issue clone issue with .gdb , .loz, & .las files","startedAt":"2022-05-12T15:36:33Z","lastAt":"2022-05-13T01:49:09Z","messageCount":2,"participants":["Robert Brown","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"455207","messageId":"SA1PR05MB8454906260C1851A39813916ACCB9@SA1PR05MB8454.namprd05.prod.outlook.com","threadId":"57872","inReplyTo":null,"subject":"Git issue clone issue with .gdb , .loz, & .las files","fromName":"Robert Brown","fromEmail":"rbrown@esri.com","sentAt":"2022-05-12T15:36:25Z","receivedAt":"2022-05-12T15:36:33Z","isPatch":false,"sender":{"key":"rbrown@esri.com","avatar":null},"body":"Hi team,\n\nI started a thread in GitHub, but they pointed me to you. We're having a binary comparison problems when cloning a repo in Git on Windows (git version 2.36.1.windows.1), LFS is installed but is not tracking files. \n\nSo far we have noticed  .gdb, .las, and .loz files are not even close to the same size and don't open after cloning the repo. Everything else seems to clone fine at the moment, confidence to moving to Git is a problem because of this on the team. I'm looking to figure out a way to make sure we are getting binary matched clones when doing so. We sure would appreciate any help you can give us.  \n\nWe are currently testing locally, the repo and the clone exist on the same physical PC\nWindows 20H2 (OS Build 19042.1645)\ngit version 2.36.1.windows.1 (64bit)\ngit-lfs/3.1.4 (GitHub; windows amd64; go 1.17.8)\n\nOriginal GitHub Thread\nhttps://github.com/git-lfs/git-lfs/discussions/5005\n\nRobert Brown | Sr. Performance Engineer\nEsri | 380 New York Street | Redlands, CA 92373 | USA\nT (909) 793-2853 x6618 | mailto:rbrown@esri.com | http://www.esri.com/ \n\nTHE SCIENCE OF WHERE ®\n\n"},{"id":"455252","messageId":"Yn23d9UWONDFzH7n@camp.crustytoothpaste.net","threadId":"57872","inReplyTo":"SA1PR05MB8454906260C1851A39813916ACCB9@SA1PR05MB8454.namprd05.prod.outlook.com","subject":"Re: Git issue clone issue with .gdb , .loz, & .las files","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2022-05-13T01:49:02Z","receivedAt":"2022-05-13T01:49:09Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2022-05-12 at 15:36:25, Robert Brown wrote:\n> Hi team,\n\nHey,\n\n> I started a thread in GitHub, but they pointed me to you. We're having a binary comparison problems when cloning a repo in Git on Windows (git version 2.36.1.windows.1), LFS is installed but is not tracking files. \n> \n> So far we have noticed  .gdb, .las, and .loz files are not even close to the same size and don't open after cloning the repo. Everything else seems to clone fine at the moment, confidence to moving to Git is a problem because of this on the team. I'm looking to figure out a way to make sure we are getting binary matched clones when doing so. We sure would appreciate any help you can give us.  \n\nAs I mentioned, I think Git LFS is a red herring here.  There are no\npatterns in .gitattributes, so the fact that it's installed is\nirrelevant, since it's not being used.\n\nTo summarize what I said on the Git LFS issue tracker, I think you've\nseeing a problem with Git on Windows where it doesn't always handle\nfiles larger than 4 GiB properly.  My guess is that if you created the\nrepository in WSL or on a Linux box, things would work, provided you\nused a 64-bit binary.  Can you try doing that and seeing if cloning to\nanother Linux-based directory works properly for you in that case?\n-- \nbrian m. carlson (he/him or they/them)\nToronto, Ontario, CA\n"}]}