Menu
I would just like to ask what could be the meaning of this error?
error: fsmonitor_ipc__send_query: unspecified error on '.git/fsmonitor--daemon.ipc'
I'm trying to find something similar to this case but for some reason, all I see is another line error which is very similar but isn't explained why. I encountered this while I'm using Git Bash. I'm trying to utilize the Bash terminal as I want to have a different window separated when working with VS Code. Hope this become a reference for the others.
810
If fsmonitor daemon is watching a super repo and a file is modified within the working directory of a submodule, it will report the change (as happening against the super repo). However, the client will properly ignore these extra events, so performance may be affected but it will not cause an incorrect result.
Alternatively, as others have noted, you can also update Git Bash and Git (by definition, both are always updated at the same time) from the Git Bash command line, via: If you type git update, git kindly reminds you that the command has been updated to git update-git-for-windows: Please use git update-git-for-windows instead.
This daemon is a long running process used to watch a single working directory and maintain a list of the recently changed files and directories. Performance of commands such as git status can be increased if they just ask for a summary of changes to the working directory and can avoid scanning the disk.
The fsmonitor daemon does not currently know about submodules and does not know to filter out file system events that happen within a submodule. If fsmonitor daemon is watching a super repo and a file is modified within the working directory of a submodule, it will report the change (as happening against the super repo).
I, like others have mentioned, received this error, and my current Git version is 2.32.0.windows.1. I've been running this version for months and today was the first time I encountered the error.
I killed all running git.exe processes on my machine and the error went away.
Note that when you upgrade to a new version of Git, one of the things you have to do is stop all running processes of Git. I mention this because it might not be the case that this is a bug specific to 2.32 which is fixed in version 2.33, but instead, maybe it's simply the action of killing the running Git processes during the install that fixes the issue. I suppose a reboot may have fixed it as well.
166
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
