-
Notifications
You must be signed in to change notification settings - Fork 0
Improved overflow support: Fix detection of DELETED events in IndexingRescanner
#28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved overflow support: Fix detection of DELETED events in IndexingRescanner
#28
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## improved-overflow-support-main #28 +/- ##
==================================================================
+ Coverage 79.2% 80.8% +1.6%
- Complexity 119 120 +1
==================================================================
Files 16 16
Lines 539 549 +10
Branches 53 54 +1
==================================================================
+ Hits 427 444 +17
+ Misses 81 74 -7
Partials 31 31 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| // approximate `DELETED` events that happened since the previous rescan. | ||
| // Instances of this class are supposed to be used non-concurrently, so | ||
| // no synchronization to access this field is needed. | ||
| private Deque<Set<Path>> visited = new ArrayDeque<>(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can it be final?
DELETED events in IndexingRescannerDELETED events in IndexingRescanner
Before this PR, too many
DELETEDevents were issued byIndexingRescannerin the situation where the initial index is larger than the set of files in the scope of the watch. This PR adds a test to expose this misbehavior and a fix.