feat(inotify): notify a user if the max_user_watches has been reached implicitly#698
feat(inotify): notify a user if the max_user_watches has been reached implicitly#698dfaust merged 2 commits intonotify-rs:mainfrom
max_user_watches has been reached implicitly#698Conversation
…ed implicitly There was no way to detect the problem if it caused by implicitly watched directory (e.g. recursive watch). This commit gives a user the ability to handle the problem and react somehow. For example, gui app can show a notification with some instructions how to increase the value
|
Looks good. Special thanks for test! I just wish we could run it in the CI because I can see it easily being forgotten. |
I thought about it, but it requires root, and I just don't know how to solve the problem, because I did not delve into how CI works in the project.
Yep, no problem |
Ok, there is a problem:) Which version of There is already released
|
|
Yes, |
|
Thank you!
I don't know much about GitHub Actions, but after a quick search it looks like there is no root access and containerization is the only way. |
…ed implicitly (#698) * feat(inotify): notify a user if the `max_user_watches` has been reached implicitly There was no way to detect the problem if it caused by implicitly watched directory (e.g. recursive watch). This commit gives a user the ability to handle the problem and react somehow. For example, gui app can show a notification with some instructions how to increase the value * chore: changelog for (#698)
2 participants
There was no way to detect the problem if it caused by implicitly watched directory (e.g. recursive watch). This commit gives a user the ability to handle the problem and react somehow.
For example, gui app can show a notification with some instructions how to increase the value