Repository changes detection has stopped working

[Mingun]

Describe the bug When I open my big (>30000 commits) git svn repository, GitNuro shows the message "Repository changes detection has stopped working: Could not watch directory. Check if it is exists and you have read permissions". There is no pointers which directory is expected -- I have read permissions to the all directories in the project folder. GitNuro opened repository successfully, but does not see changes in it (foe example, when I modify files it not show them in the Unstaged panel).

Permissions to important files in the project root:

~/ssd/tx/git$ ls -l
итого 600
drwxr-xr-x 51 mingun mingun  12288 фев 24 12:39  ./
drwxrwxr-x  4 mingun mingun   4096 сен 10 09:55  ../
drwxr-xr-x 11 mingun mingun   4096 фев 24 12:39  .git/
-rw-rw-r--  1 mingun mingun    401 сен 20 09:13  .gitignore
...

To Reproduce I my case I just open the repository. The gitnuro.log file does not contain useful information, it has only 2 lines:

2025-02-24 12:11:50 INFO  slf4j:10 - TabViewModel - Trying to open repository /home/mingun/ssd/tx/git
2025-02-24 12:11:50 INFO  slf4j:10 - SharedRepositoryStateMa - Refreshing repository state None

Expected behavior Changes detection should work.

Screenshots

Desktop (please complete the following information):

• OS: Ubuntu 24.04.2 LTS
• Version: 1.5.0-beta01

I suggest to improve error message by including directory name to the message. Also, it should be way to manually trigger changes detection when automatic does not work.

[JetpackDuba]

There is an additional option refresh manually as well as pressing F5.

The issue is with the repository itself but not sure exactly why. Could it be an inotify limit being reached but being missreported? As there is a message foforr that. If you could give it a try it would be nice https://watchexec.github.io/docs/inotify-limits.html

Does it happen in any public repository I can use to test?

[Mingun]

There is an additional option refresh manually as well as pressing F5.

Yes, thanks. I found it in Actions menu a minute later after reporting this issue.

Could it be an inotify limit being reached but being missreported?

Probably. In the past I have problems with inotify limit, if I remember correctly, in VSCode extension. Then the problem solved just by increasing inotify limit. This is the same machine, so the limit should be already raised, but I'll check it when get access to my computer.

Does it happen in any public repository I can use to test?

I didn't check. Will try to investigate that.