{"thread":{"id":"53070","subject":"git > 2.10.1 fails to update index on macOS 10.14.5","startedAt":"2020-03-23T14:53:47Z","lastAt":"2020-03-30T11:22:01Z","messageCount":5,"participants":["Jonathan Smalls","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"393771","messageId":"7b8b23f8-e12a-bde9-4b9e-ca8c908d1203@smalls.rocks","threadId":"53070","inReplyTo":null,"subject":"git > 2.10.1 fails to update index on macOS 10.14.5","fromName":"Jonathan Smalls","fromEmail":"jon@smalls.rocks","sentAt":"2020-03-23T14:37:30Z","receivedAt":"2020-03-23T14:53:47Z","isPatch":false,"sender":{"key":"jon@smalls.rocks","avatar":null},"body":"After upgrading my work station, I found in git-2.22 that git would not \nrecognize any file changes until I ran  `git reset --hard`. I thought \nthat it was a problem with my own settings.\n\tHowever I upgraded to git-2.25, and the problem actually got worse. In \n2.25 the index still failed to update, but `git reset --hard` no longer \nhad any effect.\n\nI have not looked to find exactly where the breaking change was \nintroduced, but I have since downgraded to git-2.10.1 and now get the \nexpected behavior.\n-- \nhttp://jon.smalls.rocks\n857 301 9231\n"},{"id":"393837","messageId":"20200323231351.GD6499@camp.crustytoothpaste.net","threadId":"53070","inReplyTo":"7b8b23f8-e12a-bde9-4b9e-ca8c908d1203@smalls.rocks","subject":"Re: git > 2.10.1 fails to update index on macOS 10.14.5","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2020-03-23T23:13:51Z","receivedAt":"2020-03-23T23:13:59Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2020-03-23 at 14:37:30, Jonathan Smalls wrote:\n> After upgrading my work station, I found in git-2.22 that git would not\n> recognize any file changes until I ran  `git reset --hard`. I thought that\n> it was a problem with my own settings.\n> \tHowever I upgraded to git-2.25, and the problem actually got worse. In 2.25\n> the index still failed to update, but `git reset --hard` no longer had any\n> effect.\n\nI have a bunch of colleagues who use the latest Git on macOS, so I\nexpect it does work most of the time.  Let's see if we can figure out\nwhat's going on here.\n\nWhat exactly do you mean by \"doesn't recognize any file changes\"?  Can\nyou tell us what commands you ran and what you expected to see, and what\nyou actually saw?  That information would be helpful for us to track\ndown what might be happening.\n\nAlso, are you using any specific workflow or tool that might be related?\nAre you using an editor integration or GUI, and if so, does this happen\nwithout that editor integration or GUI as well?\n-- \nbrian m. carlson: Houston, Texas, US\nOpenPGP: https://keybase.io/bk2204\n"},{"id":"393848","messageId":"414a10db-18d4-0c19-eafe-fbb85811fffe@smalls.rocks","threadId":"53070","inReplyTo":"20200323231351.GD6499@camp.crustytoothpaste.net","subject":"Re: git > 2.10.1 fails to update index on macOS 10.14.5","fromName":"Jonathan Smalls","fromEmail":"jon@smalls.rocks","sentAt":"2020-03-24T01:36:18Z","receivedAt":"2020-03-24T01:37:37Z","isPatch":false,"sender":{"key":"jon@smalls.rocks","avatar":null},"body":"\n\nOn 3/23/20 19:13, brian m. carlson wrote:\n> What exactly do you mean by \"doesn't recognize any file changes\"?  Can\n> you tell us what commands you ran and what you expected to see, and what\n> you actually saw?  That information would be helpful for us to track\n> down what might be happening.\n\nIn git-2.22:\n\nI would write a change to a file. Running `git status` would return that \nthe working directory was clean, and `git commit .` would show that \nthere were no changes to commit.\n\tHowever I could target a specific file like `git commit test.txt`, and \ngit would successfully recognize the change, and write the commit. I \ncould also run `git reset --hard`, and that would update the index to \nreflect the change that I had just written rather than resetting the \nworking directory to match the latest commit. If I ran `git reset \n--hard` a second time, that command would reset the working directory.\n\nIn normal operation, I would expect to `git status` to recognize a \nchange in a file once it had already been added to the index. I would \nexpect `git commit .` to commit all files in the current directory, and \nsubdirectories without having to specify their file names. I would \nexpect `git reset --hard` to revert the working directory to match the \nlatest commit the first time.\n\nIn git-2.25\n\nI would write a change to a file. `git status` would continue to show \nthat the working directory was clean, but I was not longer able to \ntarget a particular file to force a commit. `git reset --hard` had no \neffect, and still showed that the working directory was clean without \nresetting the working directory.\n\tTo successfully commit a file I would have to run `git rm --cached \ntest.txt` to target a file, and then `git add test.txt` for git to \nupdate its index, and recognize the change.\n\nI would expect the same normal operation in git-2.25.\n\n> \n> Also, are you using any specific workflow or tool that might be related?\n> Are you using an editor integration or GUI, and if so, does this happen\n> without that editor integration or GUI as well?\n\nI use git on the command line, so there should be no external \ninterference with its normal function.\n"},{"id":"393912","messageId":"20200324235934.GI6499@camp.crustytoothpaste.net","threadId":"53070","inReplyTo":"414a10db-18d4-0c19-eafe-fbb85811fffe@smalls.rocks","subject":"Re: git > 2.10.1 fails to update index on macOS 10.14.5","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2020-03-24T23:59:34Z","receivedAt":"2020-03-24T23:59:43Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2020-03-24 at 01:36:18, Jonathan Smalls wrote:\n> \n> \n> On 3/23/20 19:13, brian m. carlson wrote:\n> > What exactly do you mean by \"doesn't recognize any file changes\"?  Can\n> > you tell us what commands you ran and what you expected to see, and what\n> > you actually saw?  That information would be helpful for us to track\n> > down what might be happening.\n> \n> In git-2.22:\n> \n> I would write a change to a file. Running `git status` would return that the\n> working directory was clean, and `git commit .` would show that there were\n> no changes to commit.\n> \tHowever I could target a specific file like `git commit test.txt`, and git\n> would successfully recognize the change, and write the commit. I could also\n> run `git reset --hard`, and that would update the index to reflect the\n> change that I had just written rather than resetting the working directory\n> to match the latest commit. If I ran `git reset --hard` a second time, that\n> command would reset the working directory.\n\nDoes running \"ls -l\" on the file before and after show different\ntimestamps and file sizes?  Does \"git config -l | grep -iE 'checkstat|ctime'\"\nshow anything?  Can you use the stat(1) command to tell us whether the\nchange results in a device or inode number change (if that's possible\nusing the macOS version)?\n-- \nbrian m. carlson: Houston, Texas, US\nOpenPGP: https://keybase.io/bk2204\n"},{"id":"394334","messageId":"909fa74a-2310-c744-6b85-fac3a5bd5081@smalls.rocks","threadId":"53070","inReplyTo":"20200324235934.GI6499@camp.crustytoothpaste.net","subject":"Re: git > 2.10.1 fails to update index on macOS 10.14.5","fromName":"Jonathan Smalls","fromEmail":"jon@smalls.rocks","sentAt":"2020-03-30T11:20:35Z","receivedAt":"2020-03-30T11:22:01Z","isPatch":false,"sender":{"key":"jon@smalls.rocks","avatar":null},"body":"I also need to specify, it looks like I was on git version 2.21.0, not \n2.22.0.\n\nOn 3/24/20 19:59, brian m. carlson wrote:\n> Does running \"ls -l\" on the file before and after show different\n> timestamps and file sizes? \n\nChanging the index file updated the file modification time appropriately.\n\n--\n\nMar30 0715.19 [jsmalls:~/Documents … c310/lorenzCurve] master+\n     >> vim index.py\n\n     Mar30 0715.31 [jsmalls:~/Documents … c310/lorenzCurve] master+ 8s\n     >> ls -l\ntotal 56\n-rw-r--r--  1 jsmalls  staff   1650 Mar 30 07:15 index.py\n-rw-r--r--@ 1 jsmalls  staff  16878 Mar 29 20:10 lorenzCurve.png\n-rw-r--r--@ 1 jsmalls  staff   1800 Mar 26 09:05 pop2010.npy\n\nDoes \"git config -l | grep -iE 'checkstat|ctime'\"\n> show anything? Can you use the stat(1) command to tell us whether the\n> change results in a device or inode number change (if that's possible\n> using the macOS version)?\n\nThe git config command returns an empty result. I am not sure what I \nshould see in the stat command, but I have included the result here.\n\n--\n\nMar30 0715.40 [jsmalls:~/Documents … c310/lorenzCurve] master+\n     >> git config -l | grep -iE 'checkstat|ctime'\n\n     Mar30 0716.19 [jsmalls:~/Documents … c310/lorenzCurve] master+ 1\n     >> stat\n1054203952 723 crw--w---- 1 jsmalls tty 268435456 0 \"Mar 30 07:16:43 \n2020\" \"Mar 30 07:16:43 2020\" \"Mar 30 07:16:43 2020\" \"Dec 31 19:00:00 \n1969\" 131072 0 0 (stdin)\n\n"}]}