Skip to content
This repository has been archived by the owner on Jan 18, 2023. It is now read-only.

Shouldn't start watching .git #18

Closed
nathany opened this issue Nov 14, 2014 · 3 comments
Closed

Shouldn't start watching .git #18

nathany opened this issue Nov 14, 2014 · 3 comments
Assignees
Labels

Comments

@nathany
Copy link
Owner

nathany commented Nov 14, 2014

An event (not sure which) triggered the following:

Watching path .git/hooks
Watching path .git/info
Watching path .git/logs
Watching path .git/objects
Watching path .git/refs
Watching path .git/objects/f5
Watching path .git/objects/5a
Watching path .git/objects/b4

This was an existing git repository, so the .git folder was not created. Using OS X (kqueue).

Seems like there may be a regression in the recent changes. Though it's not obvious to me what happened yet.

@nathany
Copy link
Owner Author

nathany commented Dec 13, 2014

With -debug it becomes more obvious.

Detected new directory .git/hooks
Watching path .git/hooks

It's checking hooks, which isn't a hidden directory, but is contained inside a hidden directory.

This happens to me when I switch to Tower.

@nathany
Copy link
Owner Author

nathany commented Dec 13, 2014

The question is why it's seeing changes in .git at all. And indeed, it does not see changes when using fsnotify 1.0.4 (kqueue), but does with master.

Looks like an fsnotify regression. 😦

@nathany
Copy link
Owner Author

nathany commented Dec 13, 2014

This bug in fsnotify would impact OS X and BSD users. It is now fixed on fsnotify master.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant