-
-
Notifications
You must be signed in to change notification settings - Fork 708
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
KeyError: 731 #117
Comments
That's not fixed yet, and it isn't so random as it perhaps seems. I'm having this issue "consistently" here. I mean, all the time (on every run), unless I add an artificial 50ms sleep to the event handler:
|
I was checking here the cause, as it seems it's due to a path that appears twice in the
Should I open a new issue? |
- This is related to gorakhargosh#117 and gorakhargosh#233 - It's about a single path that is has 2 wd values, i.e., a subdirectory path that was created again before the "bookkeeping removal" event (IN_IGNORE) of a deletion was processed - The test is using a stochastical approach to reach the bug, in the sense that being "fast" isn't enough to enforce a particular event order; however, a "lucky" event synchronization seems extremely rare and the package should pass on every case - Even with an unknown order for the events, the test is counting and enforces: - Watchdog emits the 120 events that happened - Specific number of events for each type - Order constraing as required for minimal consistency (e.g. not deleting a directory that wasn't created)
- The call on inotify_event.is_ignored was removing the wrong wd, due to another wd with the same path (self._wd_for_path[src_path] was replaced) - Fix gorakhargosh#117 and gorakhargosh#233 - Still not enough to fix every bug regarding fast/unordered events, but doesn't crash anymore
- This is related to gorakhargosh#117 and gorakhargosh#233 - It's about a single path that is has 2 wd values, i.e., a subdirectory path that was created again before the "bookkeeping removal" event (IN_IGNORE) of a deletion was processed - The test is using a stochastical approach to reach the bug, in the sense that being "fast" isn't enough to enforce a particular event order; however, a "lucky" event synchronization seems extremely rare and the package should pass on every case - Even with an unknown order for the events, the test is counting and enforces: - Watchdog emits the 120 events that happened - Specific number of events for each type - Order constraing as required for minimal consistency (e.g. not deleting a directory that wasn't created)
- The call on inotify_event.is_ignored was removing the wrong wd, due to another wd with the same path (self._wd_for_path[src_path] was replaced) - Fix gorakhargosh#117 and gorakhargosh#233 - Still not enough to fix every bug regarding fast/unordered events, but doesn't crash anymore
Inotify event order/duplication, fix gorakhargosh#117 and gorakhargosh#233
First of all, thanks for this awesome project. It's really useful.
When I use watchdog intensively, I have sometime this kind of exception:
Edit issue:
Here's exactly the same stacktrace (with the error at the same line) but the KeyError is now 730. Could you help me ?
The text was updated successfully, but these errors were encountered: