Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue) 1. create commit in master (default branch) 2. amend it 3. send commit to the upstream via pull request 4. after commit is merged into the upstream, execute `git pull --rebase=merges --ff --autostash` 5. run git status
What did you expect to happen? (Expected behavior) Git will print repository status
What happened instead? (Actual behavior) BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index (547842 > 54) error: git died of signal 6
What's different between what you expected and what actually happened? I don't expect git to come into broken state after executing ordinary commands.
Anything else you want to add: I have this options set in the config: core.fsmonitor=true core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true core.ignorecase=true core.precomposeunicode=true core.fsmonitor=true core.fscache=false core.preloadindex=true core.multipackindex=true core.splitindex=true core.untrackedcache=true submodule.active=. branch.master.remote=origin branch.master.merge=refs/heads/master status.showuntrackedfiles=all
Please review the rest of the bug report below. You can delete any lines you don't wish to share.
[System Info] git version: git version 2.39.1 cpu: arm64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Darwin 22.5.0 Darwin Kernel Version 22.5.0: Mon Apr 24 20:52:24 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6000 arm64 compiler info: clang: 14.0.0 (clang-1400.0.29.202) libc info: no libc information available $SHELL (typically, interactive shell): /bin/zsh
[Enabled Hooks]
