fix: INotifyWatcher may raise events with no paths

CHANGELOG.md

@@ -2,8 +2,10 @@
 
 ## notify 8.2.0 (unreleased)
 - FEATURE: notify a user if the `max_user_watches` has been reached implicitly (`INotifyWatcher`) [#698]
+- FIX: `INotifyWatcher` ignores events with unknown watch descriptors (instead of `EventMask::Q_OVERFLOW`) [#700]
 
 [#698]: https://github.com/notify-rs/notify/pull/698
+[#700]: https://github.com/notify-rs/notify/pull/700
 
 ## notify 8.1.0 (2025-07-03)
 - FEATURE: added support for the [`flume`](https://docs.rs/flume) crate

notify-debouncer-full/src/lib.rs

@@ -279,7 +279,13 @@ impl<T: FileIdCache> DebounceDataInner<T> {
             return;
         }
 
-        let path = &event.paths[0];
+        let path = match event.paths.first() {
+            Some(path) => path,
+            None => {
+                log::info!("skipping event with no paths: {event:?}");
+                return;
+            }
+        };
 
         match &event.kind {
             EventKind::Create(_) => {
@@ -775,6 +781,7 @@ mod tests {
             "add_create_event",
             "add_create_event_after_remove_event",
             "add_create_dir_event_twice",
+            "add_event_with_no_paths_is_ok",
             "add_modify_content_event_after_create_event",
             "add_rename_from_event",
             "add_rename_from_event_after_create_event",

notify-debouncer-full/test_cases/add_event_with_no_paths_is_ok.hjson

@@ -0,0 +1,13 @@
+// https://github.com/notify-rs/notify/issues/678
+//
+// There was a bug in INotifyWatcher that causes producing events with no paths.
+// Debouncer should ignore this kind of events
+{
+    state: {}
+    events: [
+        { kind: "create-folder", paths: [] }
+    ]
+    expected: {
+        queues: {}
+    }
+}