Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error: watch EPERM at errnoException (fs.js:1019:11) on Eclipse clean #140

Closed
ghost opened this issue Aug 23, 2013 · 5 comments
Closed

Error: watch EPERM at errnoException (fs.js:1019:11) on Eclipse clean #140

ghost opened this issue Aug 23, 2013 · 5 comments
Labels
duplicate

Comments

@ghost
Copy link

ghost commented Aug 23, 2013

gui writes connection lost followed by "something went wrong"

events.js:72
throw er; // Unhandled 'error' event
^
Error: watch EPERM
at errnoException (fs.js:1019:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1037:26)

windows 7 64bit, ungit 0.1.6, node v0.10.3
@ghost
Copy link
Author

ghost commented Aug 23, 2013

the same with node 0.10.17

@FredrikNoren
Copy link
Owner

Closing as duplicate of #118

@Subash
Copy link

Subash commented Sep 5, 2013

@FredrikNoren I don't think they are same.

@FredrikNoren
Copy link
Owner

@sbspk Ops yeah you're right

@FredrikNoren FredrikNoren reopened this Sep 5, 2013
FredrikNoren added a commit that referenced this issue Sep 9, 2013
@FredrikNoren
Don't watch all files. #36, #90, #118, #140, #192
4c48f93 
Replaced the watchr module with a normal fs.watch. However, fs.watch isn't prefect on all platforms (on Windows changes in subdirectories doesn't get picked up) so there's also an "re-activity" hack to detect when a user is interested in ungit (which triggers a refresh)
@FredrikNoren
Copy link
Owner

This should be solved with the above commit (haven't seen any occurrences in the bugtracker), closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@FredrikNoren @Subash