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: ENOENT, stat 'my file' causes connection lost. #192

Closed
raspofabs opened this issue Sep 7, 2013 · 1 comment
Closed

Error: ENOENT, stat 'my file' causes connection lost. #192

raspofabs opened this issue Sep 7, 2013 · 1 comment

Comments

@raspofabs
Copy link 

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: ENOENT, stat '/home/raspo/adminpanel/stat.db-journal'

I presume this is because ungit noticed the file exists, then by the time it got around to calling stat on it, it was gone. This seems like something you can catch and just ignore rather than crashing on. (I don't actually know how to code node.js stuff, so I don't know how difficult it actually is to catch the error, but 'file going away' seems like a thing that should be handled.)
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

@raspofabs I've had lots of other issues with the way ungit's watching files so I'm trying a different approach; the commit above should make sure there's no more stating of files like that. Closing this for now but if the problem still remains with this fix please re-open.

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

No branches or pull requests
2 participants
@FredrikNoren @raspofabs