-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
feat(lsp): drop fswatch, use inotifywait #29374
base: master
Are you sure you want to change the base?
Conversation
c0691c7
to
16ea529
Compare
The package |
16ea529
to
844093c
Compare
runtime/doc/news.txt
Outdated
@@ -54,7 +54,9 @@ EVENTS | |||
|
|||
LSP | |||
|
|||
• TODO | |||
• The watchfunc backend was implemented with fswatch, but deactivated by |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if we need to mention this here since it was deactivated by default, and so it's not like a breaking change or anything.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where do I activate it by default? :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found it and enabled it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we want to enable it. Anything that uses inotify is going to have the same problems. It wasn't startup-time of fswatch that was the issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was the problem?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Users kept hitting the limits of inotify and getting error messages.
Note libuv also uses inotify internally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've removed it and improved the documentation.
However I think it should be documented how to enable inotify as watchfunc. I haven't found anything yet. Any suggestion where to do that?
844093c
to
c8f72b0
Compare
84f0337
to
30e95b2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test failures look related?
30e95b2
to
3770c73
Compare
inotify-tools needs to be installed on the CI image, I'm not sure how to do that. Update: Might have found it. |
This patch replaces fswatch with inotifywait from inotify-toools: https://github.com/inotify-tools/inotify-tools fswatch takes ~1min to set up recursively for the Samba source code directory. inotifywait needs less than a second to do the same thing. emcrisostomo/fswatch#321 Also it fswatch seems to be unmaintained in the meantime. Signed-off-by: Andreas Schneider <[email protected]>
3770c73
to
8823dce
Compare
This patch replaces fswatch with inotifywait from inotify-toools:
https://github.com/inotify-tools/inotify-tools
fswatch takes ~1min to set up recursively for the Samba source code directory. inotifywait needs less than a second to do the same thing.
emcrisostomo/fswatch#321
Also fswatch seems to be unmaintained in the meantime.