git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Fedor Bocharov <fedor.bocharov@jetbrains.com>
To: git@vger.kernel.org
Subject: BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index
Date: Sat, 3 Jun 2023 20:18:23 +0200	[thread overview]
Message-ID: <2B864C9E-9693-49F2-AE50-CB56DE872AB9@jetbrains.com> (raw)

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]


             reply	other threads:[~2023-06-03 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03 18:18 Fedor Bocharov [this message]
2023-06-04  4:38 ` BUG: fsmonitor.c:21: fsmonitor_dirty has more entries than the index Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2022-07-19 21:36 Kache Hit
2022-07-19 22:20 ` Kache Hit
2022-07-29 15:59   ` Johannes Schindelin
2022-08-23  4:53     ` Kache Hit
2023-11-04 22:05       ` Kache Hit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2B864C9E-9693-49F2-AE50-CB56DE872AB9@jetbrains.com \
    --to=fedor.bocharov@jetbrains.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).