-
-
Notifications
You must be signed in to change notification settings - Fork 958
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 cannot start: path is too long #5107
Comments
What's coc.nvim will subscribe a pattern to watchman to monitor file changes, the
Can't understand this. |
Seems
When the current working directory is my home directory, the error messages won't be displayed. |
I guess the UNIX socket path is too long? For example, watchman can start successfully with this command: But not this: Also, before I upgrade watchman from |
I'm using watchman
|
@scientificworld I have the same problem on MacOS. Homebrew formula is changed so that default statedir is empty. That's why it started happening from while ago. Here is the change I suspect is the culprit: |
Maybe my username is longer so it reaches the length limit of socket path. |
Thank you, after I revert the changes and rebuild from source, it works again! Shall this be reported to Homebrew? |
Closes this as it's not coc.nvim's issue. |
@scientificworld I created an issue in the Homebrew repo. Hopefully, it will be resolved quickly. |
A workaround while we work out a proper fix is to do
Note that this workaround is insecure on multi-user systems. |
Result from CocInfo
The version of watchman is
2024.08.05.00
, installed from Homebrew.Describe the bug
When opening file outside the home directory, the error will be triggered.
Reproduce the bug
Change current directory and open any file.
Screenshots (optional)
The text was updated successfully, but these errors were encountered: