Skip to content

Conversation

@riberk
Copy link
Contributor

@riberk riberk commented Jul 15, 2025

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

…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
@dfaust
Copy link
Member

dfaust commented Jul 15, 2025

Looks good. Special thanks for test! I just wish we could run it in the CI because I can see it easily being forgotten.
Just one small think. Can you please add a change-log entry.

@riberk
Copy link
Contributor Author

riberk commented Jul 15, 2025

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.

  • If CI runs with root privileges, then I can just add runtime check if the user is root or not and run the test only for the root user.
  • If CI runs WITHOUT the privileges, then it requires more complex solution with some kind of containerization / virtualization, and I think it doesn't worth it

Can you please add a change-log entry.

Yep, no problem

@riberk
Copy link
Contributor Author

riberk commented Jul 15, 2025

Yep, no problem

Ok, there is a problem:)

Which version of notify should it be?

There is already released 8.1.0 in CHANGELOG.md

notify 8.2.0 (unreleased)?

@dfaust
Copy link
Member

dfaust commented Jul 15, 2025

Yes, notify 8.2.0 is good. Or leave it empty.

@dfaust
Copy link
Member

dfaust commented Jul 15, 2025

Thank you!

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.

* If CI runs with root privileges, then I can just add runtime check if the user is root or not and run the test only for the root user.

* If CI runs WITHOUT the privileges, then it requires more complex solution with some kind of containerization / virtualization, and I think it doesn't worth it

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.

@dfaust dfaust merged commit 394ef18 into notify-rs:main Jul 15, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants