{"thread":{"id":"58192","subject":"BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index","startedAt":"2022-07-19T21:36:52Z","lastAt":"2023-11-04T22:06:20Z","messageCount":5,"participants":["Kache Hit","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"459474","messageId":"CAC7ZvybvykKQyMWcZoKXxFDu_amnkxZCDq2C6KHoyhmHN2tcKw@mail.gmail.com","threadId":"58192","inReplyTo":null,"subject":"BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index","fromName":"Kache Hit","fromEmail":"kache.hit@gmail.com","sentAt":"2022-07-19T21:36:35Z","receivedAt":"2022-07-19T21:36:52Z","isPatch":false,"sender":{"key":"kache.hit@gmail.com","avatar":null},"body":"Hi. Output of git bugreport:\n\n---\n\nThank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\n\nWanted to retain git tree structure when pulling latest and rebasing.\nFirst indication of error was the `rebase -r` of the merge commit\n\nWhat did you expect to happen? (Expected behavior)\n\nsuccessful --rebase-merges rebase of my commits on top of master\n\nWhat happened instead? (Actual behavior)\n\n```sh\n❯ git rebase -r master\nBUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n(179457 > 1040)\nzsh: abort      git rebase -r master\n```\n\nWhat's different between what you expected and what actually happened?\n\nAnything else you want to add:\n\nI'm currently \"stuck\" in this state, not sure how to recover or repro:\n\n```sh\n❯ git s\nBUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n(179457 > 1040)\nerror: git died of signal 6\n\n❯ git log\n\n❯ git d head~\nerror: git died of signal 6\nBUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n(179457 > 1040)\n\n❯ git log # works\n\n❯ git status\nBUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n(179457 > 1040)\nzsh: abort      git status\n\n❯ git commit --amend\nBUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n(179457 > 1040)\nzsh: abort      git commit --amend\n\n❯ git checkout head\nfatal: Unable to create '/Users/XXXXX/YYYYY/.git/index.lock': File exists.\n\nAnother git process seems to be running in this repository, e.g.  #\nAll of this was run while git bugreport was running\nan editor opened by 'git commit'. Please make sure all processes\nare terminated then try again. If it still fails, a git process\nmay have crashed in this repository earlier:\nremove the file manually to continue.\n\n❯ rm /Users/XXXXX/YYYYY/.git/index.lock\n\n❯ git checkout head\nBUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n(179457 > 1040)\nzsh: abort      git checkout head\n\n❯ git checkout head\nfatal: Unable to create '/Users/XXXXX/YYYYY/.git/index.lock': File exists.\n\nAnother git process seems to be running in this repository, e.g.\nan editor opened by 'git commit'. Please make sure all processes\nare terminated then try again. If it still fails, a git process\nmay have crashed in this repository earlier:\nremove the file manually to continue.\n```\n\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.37.1\ncpu: x86_64\nno commit associated with this build\nsizeof-long: 8\nsizeof-size_t: 8\nshell-path: /bin/sh\nfeature: fsmonitor--daemon\nuname: Darwin 20.6.0 Darwin Kernel Version 20.6.0: Tue Feb 22 21:10:41\nPST 2022; root:xnu-7195.141.26~1/RELEASE_X86_64 x86_64\ncompiler info: clang: 13.0.0 (clang-1300.0.29.30)\nlibc info: no libc information available\n$SHELL (typically, interactive shell): /bin/zsh\n\n\n[Enabled Hooks]\npre-commit\npre-push\n"},{"id":"459477","messageId":"CAC7ZvyYGSa-sH1LZ8Lo=NRXbvJsujgFYGPOQR5ZwGHJHZgoDzA@mail.gmail.com","threadId":"58192","inReplyTo":"CAC7ZvybvykKQyMWcZoKXxFDu_amnkxZCDq2C6KHoyhmHN2tcKw@mail.gmail.com","subject":"Re: BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index","fromName":"Kache Hit","fromEmail":"kache.hit@gmail.com","sentAt":"2022-07-19T22:20:07Z","receivedAt":"2022-07-19T22:20:25Z","isPatch":false,"sender":{"key":"kache.hit@gmail.com","avatar":null},"body":"A thought: the 179457 is reminiscent of something else I did just before this:\n\nI was doing some \"code archeology\" and was headlessly checking out\nsome old SHAs in this large monorepo.\nDuring checkout, it said it was updating 174823 files in total.\n\nOn Tue, Jul 19, 2022 at 2:36 PM Kache Hit <kache.hit@gmail.com> wrote:\n>\n> Hi. Output of git bugreport:\n>\n> ---\n>\n> Thank you for filling out a Git bug report!\n> Please answer the following questions to help us understand your issue.\n>\n> What did you do before the bug happened? (Steps to reproduce your issue)\n>\n> Wanted to retain git tree structure when pulling latest and rebasing.\n> First indication of error was the `rebase -r` of the merge commit\n>\n> What did you expect to happen? (Expected behavior)\n>\n> successful --rebase-merges rebase of my commits on top of master\n>\n> What happened instead? (Actual behavior)\n>\n> ```sh\n> ❯ git rebase -r master\n> BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> (179457 > 1040)\n> zsh: abort      git rebase -r master\n> ```\n>\n> What's different between what you expected and what actually happened?\n>\n> Anything else you want to add:\n>\n> I'm currently \"stuck\" in this state, not sure how to recover or repro:\n>\n> ```sh\n> ❯ git s\n> BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> (179457 > 1040)\n> error: git died of signal 6\n>\n> ❯ git log\n>\n> ❯ git d head~\n> error: git died of signal 6\n> BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> (179457 > 1040)\n>\n> ❯ git log # works\n>\n> ❯ git status\n> BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> (179457 > 1040)\n> zsh: abort      git status\n>\n> ❯ git commit --amend\n> BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> (179457 > 1040)\n> zsh: abort      git commit --amend\n>\n> ❯ git checkout head\n> fatal: Unable to create '/Users/XXXXX/YYYYY/.git/index.lock': File exists.\n>\n> Another git process seems to be running in this repository, e.g.  #\n> All of this was run while git bugreport was running\n> an editor opened by 'git commit'. Please make sure all processes\n> are terminated then try again. If it still fails, a git process\n> may have crashed in this repository earlier:\n> remove the file manually to continue.\n>\n> ❯ rm /Users/XXXXX/YYYYY/.git/index.lock\n>\n> ❯ git checkout head\n> BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> (179457 > 1040)\n> zsh: abort      git checkout head\n>\n> ❯ git checkout head\n> fatal: Unable to create '/Users/XXXXX/YYYYY/.git/index.lock': File exists.\n>\n> Another git process seems to be running in this repository, e.g.\n> an editor opened by 'git commit'. Please make sure all processes\n> are terminated then try again. If it still fails, a git process\n> may have crashed in this repository earlier:\n> remove the file manually to continue.\n> ```\n>\n>\n> Please review the rest of the bug report below.\n> You can delete any lines you don't wish to share.\n>\n>\n> [System Info]\n> git version:\n> git version 2.37.1\n> cpu: x86_64\n> no commit associated with this build\n> sizeof-long: 8\n> sizeof-size_t: 8\n> shell-path: /bin/sh\n> feature: fsmonitor--daemon\n> uname: Darwin 20.6.0 Darwin Kernel Version 20.6.0: Tue Feb 22 21:10:41\n> PST 2022; root:xnu-7195.141.26~1/RELEASE_X86_64 x86_64\n> compiler info: clang: 13.0.0 (clang-1300.0.29.30)\n> libc info: no libc information available\n> $SHELL (typically, interactive shell): /bin/zsh\n>\n>\n> [Enabled Hooks]\n> pre-commit\n> pre-push\n"},{"id":"460230","messageId":"orr5573q-7148-84ro-9rpq-nr7411s894r9@tzk.qr","threadId":"58192","inReplyTo":"CAC7ZvyYGSa-sH1LZ8Lo=NRXbvJsujgFYGPOQR5ZwGHJHZgoDzA@mail.gmail.com","subject":"Re: BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2022-07-29T15:59:54Z","receivedAt":"2022-07-29T16:00:02Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Kache,\n\nOn Tue, 19 Jul 2022, Kache Hit wrote:\n\n> A thought: the 179457 is reminiscent of something else I did just before this:\n>\n> I was doing some \"code archeology\" and was headlessly checking out\n> some old SHAs in this large monorepo.\n> During checkout, it said it was updating 174823 files in total.\n\nDo you think it would be possible to whittle this down a bit, and maybe\nattempt to come up with a reproducible example? Something like what is\ndescribed in https://stackoverflow.com/help/mcve.\n\nIf all else fails, and you _only_ manage to reproduce it in the original\nrepository, could you at least try to figure out a reliable way to get the\nGit index into the indicated state (if I were you, I would start off by\nswitching to the pre-rebase revision, deleting `.git/index` and then\nrunning `git reset --hard` and then see whether the bug can be\nreproduced)?\n\nCiao,\nJohannes\n\n>\n> On Tue, Jul 19, 2022 at 2:36 PM Kache Hit <kache.hit@gmail.com> wrote:\n> >\n> > Hi. Output of git bugreport:\n> >\n> > ---\n> >\n> > Thank you for filling out a Git bug report!\n> > Please answer the following questions to help us understand your issue.\n> >\n> > What did you do before the bug happened? (Steps to reproduce your issue)\n> >\n> > Wanted to retain git tree structure when pulling latest and rebasing.\n> > First indication of error was the `rebase -r` of the merge commit\n> >\n> > What did you expect to happen? (Expected behavior)\n> >\n> > successful --rebase-merges rebase of my commits on top of master\n> >\n> > What happened instead? (Actual behavior)\n> >\n> > ```sh\n> > ❯ git rebase -r master\n> > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > (179457 > 1040)\n> > zsh: abort      git rebase -r master\n> > ```\n> >\n> > What's different between what you expected and what actually happened?\n> >\n> > Anything else you want to add:\n> >\n> > I'm currently \"stuck\" in this state, not sure how to recover or repro:\n> >\n> > ```sh\n> > ❯ git s\n> > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > (179457 > 1040)\n> > error: git died of signal 6\n> >\n> > ❯ git log\n> >\n> > ❯ git d head~\n> > error: git died of signal 6\n> > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > (179457 > 1040)\n> >\n> > ❯ git log # works\n> >\n> > ❯ git status\n> > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > (179457 > 1040)\n> > zsh: abort      git status\n> >\n> > ❯ git commit --amend\n> > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > (179457 > 1040)\n> > zsh: abort      git commit --amend\n> >\n> > ❯ git checkout head\n> > fatal: Unable to create '/Users/XXXXX/YYYYY/.git/index.lock': File exists.\n> >\n> > Another git process seems to be running in this repository, e.g.  #\n> > All of this was run while git bugreport was running\n> > an editor opened by 'git commit'. Please make sure all processes\n> > are terminated then try again. If it still fails, a git process\n> > may have crashed in this repository earlier:\n> > remove the file manually to continue.\n> >\n> > ❯ rm /Users/XXXXX/YYYYY/.git/index.lock\n> >\n> > ❯ git checkout head\n> > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > (179457 > 1040)\n> > zsh: abort      git checkout head\n> >\n> > ❯ git checkout head\n> > fatal: Unable to create '/Users/XXXXX/YYYYY/.git/index.lock': File exists.\n> >\n> > Another git process seems to be running in this repository, e.g.\n> > an editor opened by 'git commit'. Please make sure all processes\n> > are terminated then try again. If it still fails, a git process\n> > may have crashed in this repository earlier:\n> > remove the file manually to continue.\n> > ```\n> >\n> >\n> > Please review the rest of the bug report below.\n> > You can delete any lines you don't wish to share.\n> >\n> >\n> > [System Info]\n> > git version:\n> > git version 2.37.1\n> > cpu: x86_64\n> > no commit associated with this build\n> > sizeof-long: 8\n> > sizeof-size_t: 8\n> > shell-path: /bin/sh\n> > feature: fsmonitor--daemon\n> > uname: Darwin 20.6.0 Darwin Kernel Version 20.6.0: Tue Feb 22 21:10:41\n> > PST 2022; root:xnu-7195.141.26~1/RELEASE_X86_64 x86_64\n> > compiler info: clang: 13.0.0 (clang-1300.0.29.30)\n> > libc info: no libc information available\n> > $SHELL (typically, interactive shell): /bin/zsh\n> >\n> >\n> > [Enabled Hooks]\n> > pre-commit\n> > pre-push\n>\n"},{"id":"461831","messageId":"CAC7ZvyaQpYiVAszu_Oe5UoKgpe48dRJ8i1O8hLNOSo3UXfPVug@mail.gmail.com","threadId":"58192","inReplyTo":"orr5573q-7148-84ro-9rpq-nr7411s894r9@tzk.qr","subject":"Re: BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index","fromName":"Kache Hit","fromEmail":"kache.hit@gmail.com","sentAt":"2022-08-23T04:53:33Z","receivedAt":"2022-08-23T04:54:16Z","isPatch":false,"sender":{"key":"kache.hit@gmail.com","avatar":null},"body":"Hi,\n\nI've not been able to successfully repro this after managing to\nrecover from it by rebuilding the index:\nhttps://stackoverflow.com/questions/73044253\n\nI'm sorry I couldn't be more helpful.\n\nOn Fri, Jul 29, 2022 at 8:59 AM Johannes Schindelin\n<Johannes.Schindelin@gmx.de> wrote:\n>\n> Hi Kache,\n>\n> On Tue, 19 Jul 2022, Kache Hit wrote:\n>\n> > A thought: the 179457 is reminiscent of something else I did just before this:\n> >\n> > I was doing some \"code archeology\" and was headlessly checking out\n> > some old SHAs in this large monorepo.\n> > During checkout, it said it was updating 174823 files in total.\n>\n> Do you think it would be possible to whittle this down a bit, and maybe\n> attempt to come up with a reproducible example? Something like what is\n> described in https://stackoverflow.com/help/mcve.\n>\n> If all else fails, and you _only_ manage to reproduce it in the original\n> repository, could you at least try to figure out a reliable way to get the\n> Git index into the indicated state (if I were you, I would start off by\n> switching to the pre-rebase revision, deleting `.git/index` and then\n> running `git reset --hard` and then see whether the bug can be\n> reproduced)?\n>\n> Ciao,\n> Johannes\n>\n> >\n> > On Tue, Jul 19, 2022 at 2:36 PM Kache Hit <kache.hit@gmail.com> wrote:\n> > >\n> > > Hi. Output of git bugreport:\n> > >\n> > > ---\n> > >\n> > > Thank you for filling out a Git bug report!\n> > > Please answer the following questions to help us understand your issue.\n> > >\n> > > What did you do before the bug happened? (Steps to reproduce your issue)\n> > >\n> > > Wanted to retain git tree structure when pulling latest and rebasing.\n> > > First indication of error was the `rebase -r` of the merge commit\n> > >\n> > > What did you expect to happen? (Expected behavior)\n> > >\n> > > successful --rebase-merges rebase of my commits on top of master\n> > >\n> > > What happened instead? (Actual behavior)\n> > >\n> > > ```sh\n> > > ❯ git rebase -r master\n> > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > (179457 > 1040)\n> > > zsh: abort      git rebase -r master\n> > > ```\n> > >\n> > > What's different between what you expected and what actually happened?\n> > >\n> > > Anything else you want to add:\n> > >\n> > > I'm currently \"stuck\" in this state, not sure how to recover or repro:\n> > >\n> > > ```sh\n> > > ❯ git s\n> > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > (179457 > 1040)\n> > > error: git died of signal 6\n> > >\n> > > ❯ git log\n> > >\n> > > ❯ git d head~\n> > > error: git died of signal 6\n> > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > (179457 > 1040)\n> > >\n> > > ❯ git log # works\n> > >\n> > > ❯ git status\n> > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > (179457 > 1040)\n> > > zsh: abort      git status\n> > >\n> > > ❯ git commit --amend\n> > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > (179457 > 1040)\n> > > zsh: abort      git commit --amend\n> > >\n> > > ❯ git checkout head\n> > > fatal: Unable to create '/Users/XXXXX/YYYYY/.git/index.lock': File exists.\n> > >\n> > > Another git process seems to be running in this repository, e.g.  #\n> > > All of this was run while git bugreport was running\n> > > an editor opened by 'git commit'. Please make sure all processes\n> > > are terminated then try again. If it still fails, a git process\n> > > may have crashed in this repository earlier:\n> > > remove the file manually to continue.\n> > >\n> > > ❯ rm /Users/XXXXX/YYYYY/.git/index.lock\n> > >\n> > > ❯ git checkout head\n> > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > (179457 > 1040)\n> > > zsh: abort      git checkout head\n> > >\n> > > ❯ git checkout head\n> > > fatal: Unable to create '/Users/XXXXX/YYYYY/.git/index.lock': File exists.\n> > >\n> > > Another git process seems to be running in this repository, e.g.\n> > > an editor opened by 'git commit'. Please make sure all processes\n> > > are terminated then try again. If it still fails, a git process\n> > > may have crashed in this repository earlier:\n> > > remove the file manually to continue.\n> > > ```\n> > >\n> > >\n> > > Please review the rest of the bug report below.\n> > > You can delete any lines you don't wish to share.\n> > >\n> > >\n> > > [System Info]\n> > > git version:\n> > > git version 2.37.1\n> > > cpu: x86_64\n> > > no commit associated with this build\n> > > sizeof-long: 8\n> > > sizeof-size_t: 8\n> > > shell-path: /bin/sh\n> > > feature: fsmonitor--daemon\n> > > uname: Darwin 20.6.0 Darwin Kernel Version 20.6.0: Tue Feb 22 21:10:41\n> > > PST 2022; root:xnu-7195.141.26~1/RELEASE_X86_64 x86_64\n> > > compiler info: clang: 13.0.0 (clang-1300.0.29.30)\n> > > libc info: no libc information available\n> > > $SHELL (typically, interactive shell): /bin/zsh\n> > >\n> > >\n> > > [Enabled Hooks]\n> > > pre-commit\n> > > pre-push\n> >\n"},{"id":"484438","messageId":"CAC7ZvyacrYUmJ6sr3YVqevM0zB9W1yQb65uHFwrevBy2K5fmjA@mail.gmail.com","threadId":"58192","inReplyTo":"CAC7ZvyaQpYiVAszu_Oe5UoKgpe48dRJ8i1O8hLNOSo3UXfPVug@mail.gmail.com","subject":"Re: BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index","fromName":"Kache Hit","fromEmail":"kache.hit@gmail.com","sentAt":"2023-11-04T22:05:40Z","receivedAt":"2023-11-04T22:06:20Z","isPatch":false,"sender":{"key":"kache.hit@gmail.com","avatar":null},"body":"Just reporting that I ran into this again, this time with some info to\nhelp repro, though the issue may be fixed already.\n\nI managed to avoid it by turning off core.splitIndex, so I'd suspected\nthe setting conflicts with feature.manyFiles.\nIt could very also be/instead conflict with fsmonitor that I also use,\nas mentioned in the similar/related thread:\nhttps://public-inbox.org/git/xmqqbkhv6dw3.fsf@gitster.g/T/#m13a5ad383f040bb3a6be7641bd04aa20424a274c\n\nWhich references a splitindex & fsmonitor bug that's since been\naddressed since 2.41:\nhttps://github.com/git/git/commit/3704fed5eae8ca2fa20bcf6adb277ee83b012ce0\n\nOn Mon, Aug 22, 2022 at 9:53 PM Kache Hit <kache.hit@gmail.com> wrote:\n>\n> Hi,\n>\n> I've not been able to successfully repro this after managing to\n> recover from it by rebuilding the index:\n> https://stackoverflow.com/questions/73044253\n>\n> I'm sorry I couldn't be more helpful.\n>\n> On Fri, Jul 29, 2022 at 8:59 AM Johannes Schindelin\n> <Johannes.Schindelin@gmx.de> wrote:\n> >\n> > Hi Kache,\n> >\n> > On Tue, 19 Jul 2022, Kache Hit wrote:\n> >\n> > > A thought: the 179457 is reminiscent of something else I did just before this:\n> > >\n> > > I was doing some \"code archeology\" and was headlessly checking out\n> > > some old SHAs in this large monorepo.\n> > > During checkout, it said it was updating 174823 files in total.\n> >\n> > Do you think it would be possible to whittle this down a bit, and maybe\n> > attempt to come up with a reproducible example? Something like what is\n> > described in https://stackoverflow.com/help/mcve.\n> >\n> > If all else fails, and you _only_ manage to reproduce it in the original\n> > repository, could you at least try to figure out a reliable way to get the\n> > Git index into the indicated state (if I were you, I would start off by\n> > switching to the pre-rebase revision, deleting `.git/index` and then\n> > running `git reset --hard` and then see whether the bug can be\n> > reproduced)?\n> >\n> > Ciao,\n> > Johannes\n> >\n> > >\n> > > On Tue, Jul 19, 2022 at 2:36 PM Kache Hit <kache.hit@gmail.com> wrote:\n> > > >\n> > > > Hi. Output of git bugreport:\n> > > >\n> > > > ---\n> > > >\n> > > > Thank you for filling out a Git bug report!\n> > > > Please answer the following questions to help us understand your issue.\n> > > >\n> > > > What did you do before the bug happened? (Steps to reproduce your issue)\n> > > >\n> > > > Wanted to retain git tree structure when pulling latest and rebasing.\n> > > > First indication of error was the `rebase -r` of the merge commit\n> > > >\n> > > > What did you expect to happen? (Expected behavior)\n> > > >\n> > > > successful --rebase-merges rebase of my commits on top of master\n> > > >\n> > > > What happened instead? (Actual behavior)\n> > > >\n> > > > ```sh\n> > > > ❯ git rebase -r master\n> > > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > > (179457 > 1040)\n> > > > zsh: abort      git rebase -r master\n> > > > ```\n> > > >\n> > > > What's different between what you expected and what actually happened?\n> > > >\n> > > > Anything else you want to add:\n> > > >\n> > > > I'm currently \"stuck\" in this state, not sure how to recover or repro:\n> > > >\n> > > > ```sh\n> > > > ❯ git s\n> > > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > > (179457 > 1040)\n> > > > error: git died of signal 6\n> > > >\n> > > > ❯ git log\n> > > >\n> > > > ❯ git d head~\n> > > > error: git died of signal 6\n> > > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > > (179457 > 1040)\n> > > >\n> > > > ❯ git log # works\n> > > >\n> > > > ❯ git status\n> > > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > > (179457 > 1040)\n> > > > zsh: abort      git status\n> > > >\n> > > > ❯ git commit --amend\n> > > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > > (179457 > 1040)\n> > > > zsh: abort      git commit --amend\n> > > >\n> > > > ❯ git checkout head\n> > > > fatal: Unable to create '/Users/XXXXX/YYYYY/.git/index.lock': File exists.\n> > > >\n> > > > Another git process seems to be running in this repository, e.g.  #\n> > > > All of this was run while git bugreport was running\n> > > > an editor opened by 'git commit'. Please make sure all processes\n> > > > are terminated then try again. If it still fails, a git process\n> > > > may have crashed in this repository earlier:\n> > > > remove the file manually to continue.\n> > > >\n> > > > ❯ rm /Users/XXXXX/YYYYY/.git/index.lock\n> > > >\n> > > > ❯ git checkout head\n> > > > BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index\n> > > > (179457 > 1040)\n> > > > zsh: abort      git checkout head\n> > > >\n> > > > ❯ git checkout head\n> > > > fatal: Unable to create '/Users/XXXXX/YYYYY/.git/index.lock': File exists.\n> > > >\n> > > > Another git process seems to be running in this repository, e.g.\n> > > > an editor opened by 'git commit'. Please make sure all processes\n> > > > are terminated then try again. If it still fails, a git process\n> > > > may have crashed in this repository earlier:\n> > > > remove the file manually to continue.\n> > > > ```\n> > > >\n> > > >\n> > > > Please review the rest of the bug report below.\n> > > > You can delete any lines you don't wish to share.\n> > > >\n> > > >\n> > > > [System Info]\n> > > > git version:\n> > > > git version 2.37.1\n> > > > cpu: x86_64\n> > > > no commit associated with this build\n> > > > sizeof-long: 8\n> > > > sizeof-size_t: 8\n> > > > shell-path: /bin/sh\n> > > > feature: fsmonitor--daemon\n> > > > uname: Darwin 20.6.0 Darwin Kernel Version 20.6.0: Tue Feb 22 21:10:41\n> > > > PST 2022; root:xnu-7195.141.26~1/RELEASE_X86_64 x86_64\n> > > > compiler info: clang: 13.0.0 (clang-1300.0.29.30)\n> > > > libc info: no libc information available\n> > > > $SHELL (typically, interactive shell): /bin/zsh\n> > > >\n> > > >\n> > > > [Enabled Hooks]\n> > > > pre-commit\n> > > > pre-push\n> > >\n"}]}