Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

[File Watchers] multiple console errors after huge update of git folder #6799

Closed
marcelgerber opened this issue Feb 7, 2014 · 6 comments
Closed

Comments

@marcelgerber
Copy link
Contributor

My file watchers just went offline after I made a big update of the brackets-todo cloned folder.

I got multiple console errors, as a result there are no updates of the folder in Brackets any more (not even with Reload file tree!).

Some screens:
Console errors
image
Git log
image
Brackets file tree
image
Explorer file tree
image

Windows 8.1, Brackets Sprint 36 Original Shell, afc14ac62

@njx
Copy link
Contributor

njx commented Feb 7, 2014

It looks like something called "ParseUtils.js" threw an error. Do you have any extensions installed?

@marcelgerber
Copy link
Contributor Author

ParseUtils.js is part of the brackets-todo extension.

@njx
Copy link
Contributor

njx commented Feb 7, 2014

Seems like it might be a bug in that extension - perhaps it isn't compatible with the new filesystem API. Can you try to reproduce with the extension uninstalled?

@marcelgerber
Copy link
Contributor Author

I couldn't repro it another time yet.
Closing for now.

@peterflynn
Copy link
Member

@SAplayer I think there are actually several issues here -- but none of them is watchers going offline. if that happens you'll explicitly see a warning saying "File watchers went offline!" or "Failed to watch root".

  • One issue is that brackets-todo is crashing. That is probably a bug in the extension.
  • Another issue is that the project tree is failing to update. That may simply be a side-effect of brackets-todo crashing in such a way that it hoses some important Brackets state. Or it could be some sort of bug in Brackets -- hard to tell without more data.
  • The last issue is the "Unable to stat changed path" spam. To the best of my knowledge this is harmless -- though it is confusing and spammy sometimes, so we could spin that off as a low-priority bug.

@peterflynn
Copy link
Member

Spun off #6803 for that last issue.

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

No branches or pull requests

3 participants