-
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
watchman writes incorrect path to com.github.facebook.watchman.plist file when installing via brew #357
Comments
The plist is generated using the path returned from I'm not sure how things got in a bad state for you, but these steps might help get things in the right state:
Can you try that and let us know how things go? |
What i did instead was uninstall the head version and installed 4.6.0. Then i updated the plist to the correct patch and rebooted. That seemed to have fixed it. |
OK, I'll close this out as I think it is a one-off. If it comes back, please re-open this and we can figure out what the trigger was! |
I think I ran into the same issue. I upgraded watchman and running It seems to be fixed with running launchtl unload, remote the plist, and then reinstall watchman |
Tracking the follow up for this in #358 |
When installing watchman via brew with
brew install watchman --HEAD
, it writes<string>/usr/local/Cellar/watchman/HEAD/libexec/bin/watchman</string>
to thecom.github.facebook.watchman.plist
filewhile in fact, the real location is something like
<string>/usr/local/Cellar/watchman/HEAD-39b814a/libexec/bin/watchman</string>
This leads to watchman hanging indefinitely on OSX with an error like
launchd checkin failed: No such process
in the watchman logsThe text was updated successfully, but these errors were encountered: