Fix: throw fsevents stream start error properly#733
Merged
JohnTitor merged 4 commits intonotify-rs:mainfrom Jan 14, 2026
Merged
Conversation
JohnTitor
force-pushed
the
fix/throw-fsevents-stream-start-error-properly
branch
from
219be54 to
38686d4
Compare
JohnTitor
reviewed
Jan 12, 2026
JohnTitor
pushed a commit
that referenced
this pull request
Jan 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fsevents seems to not allow watching more than 4096 paths at once.
But notify did not throw an error when that happened.
This PR makes the error to be thrown properly.