fix(fsevent): do not call FSEventsPurgeEventsForDeviceUpToEventId
#795
+137
−17
Conversation
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
JohnTitor
force-pushed
the
fsevent-stream-context
branch
3 times, most recently
from
6dc91be to
7739886
Compare
JohnTitor
force-pushed
the
fsevent-stream-context
branch
4 times, most recently
from
94740f9 to
7bcf716
Compare
JohnTitor
force-pushed
the
fsevent-stream-context
branch
from
7bcf716 to
a0cbbd5
Compare
JohnTitor
changed the title
FSEventsPurgeEventsForDeviceUpToEventId
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Fixes #681
I guess this technically removes the need of
FSEventsPurgeEventsForDeviceUpToEventIdbut I'm not sure we cover all the edge cases with this implmenetation.Related Issues