Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fsmonitor: fix mistyped fs_to_path_map variable
A typo was made in facfd59 when the wd_set variable was renamed to wd_to_path_map. This code path raises a NameError when inotify-watched files are removed from the filesystem: NameError: global name 'wd_to_path_set' is not defined Closes #607 Reported-by: Joshua Taylor <joshuataylorx@gmail.com> Signed-off-by: David Aguilar <davvid@gmail.com>
- Loading branch information
Showing
2 changed files
with
5 additions
and
1 deletion.
There are no files selected for viewing
This file contains 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
This file contains 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
08a9e55
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.
I was having a problem where switching branches or possibly other operations caused intermittent showing all files as modified until next manual refresh. Could this have been the cause?
08a9e55
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.
I doubt they are related. The fsmonitor code doesn't do any refreshing itself - it simply triggers a normal refresh (the same way as a manual refresh). If perhaps there is some sort of race in the refresh code, then I suppose there is a possibility that the fsmonitor code could be tickling it, but I don't think it likely.