-
Notifications
You must be signed in to change notification settings - Fork 998
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.
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
fsmonitor mercurial extension not responding #374
Comments
There's not a lot of info to go on here, and like any good problem, there are several layers of complexity to untangle. Let's look at the basic watchman configuration first of all. Below, Please run the following commands and share the output:
Please collect your watchman log file into a gist or pastebin and share it with me. https://facebook.github.io/watchman/docs/troubleshooting.html#where-are-the-logs has information on how to locate your log files. Re-enable the fsmonitor extension and run:
If it takes longer than a handful of seconds to run, please collect a sample of both the watchman server process and the python process that is behind your Please share the samples in a gist/pastebin. |
Hi Wez, Sharing the sample process for I also cannot locate the log file, I installed watchman using homebrew and log files are not in the location mentioned in the link you shared. |
I wonder if you're hitting this upgrade issue: #358 |
That worked very well. Thanks for the help. |
I was trying to clone the mozilla repository and mercurial was configured to use the fsmonitor extension. Cloning freezes at "updating to branch default". On removing the extension from .hgrc file it works fine. I am using watchman 4.7.0 on Mac OS 10.12.1 Beta (16B2548a).
The text was updated successfully, but these errors were encountered: