-
Notifications
You must be signed in to change notification settings - Fork 93
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
Watchdog error on startup: "inotify watch limit reached", #238
Comments
I also tried rolling back to the Locally bumping the inotify watches to a very large number made this work locally, but seems infeasible to tell every user to do:
Are there ways to configure which folders it won't watch by default? Can they be specified by environment variable or command line switch? When faced with some similar issues, i accepted some less-than-optimal performance for some simpler APIs with watchgod. |
It's unfortunate that when the native file watchers would be most useful (with a huge number of files), they can't be used. It's not currently possible to ignore folders because watchdog itself doesn't have an API for that. I'll have to think about how to go here... maybe the approach on |
By default this will still use
to force the usage of polling. |
Describe the bug
Thanks for this tool! Over on https://github.com/krassowski/jupyterlab-lsp/pull/493 we're trying to add
robotframework_ls 0.7.1
to our tested language servers, and use it for development.When trying to start
robotframework_ls
in either:node_modules
with 1000s of files, a few hundred lines ofrobot
)$HOME
)... in
jupyterlab-lsp
, the language server does not start/stay runningTo Reproduce
Steps to reproduce the behavior:
jupyter-lsp
(master
)then
Expected behavior
robotframework_ls
should continue to run... and/or return LSP log messagesScreenshots
Nothing much to see... all logging appears in terminal
Versions:
jupyterlab-lsp
master
Logs
Add the logs obtained when reproducing the issue.
See: https://github.com/robocorp/robotframework-lsp/blob/master/robotframework-ls/docs/reporting_issues.md for details on how to collect the logs.
with
-v
:The text was updated successfully, but these errors were encountered: