-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Extremely slow execution and timeout errors #16
Comments
Coc.nvim doesn't have code like |
Use output channel to see what happened https://github.com/neoclide/coc.nvim/wiki/Debug-language-server#using-output-channel |
Thanks for the quick reply. It seems like the second error was actually from a prettier plugin, but I still have the coc-eslint timeouts even when I disable that plugin. The output channel shows this after saving:
When I save and quit, I see this now:
|
You can try |
Eslint takes longer than 0.5s when I run it from the command-line, but the autoformatting takes significantly less time than it does with the plugin. Isn't the default value of |
Could be your other plugin fornating your code. |
Are you saying that another plugin might be calling {
"eslint.autoFix": false,
"eslint.autoFixOnSave": false,
"eslint.enable": true,
} but it goes away when I disable the plugin entirely: {
"eslint.autoFix": false,
"eslint.autoFixOnSave": false,
"eslint.enable": false,
} |
It's possible get called in your vim code, or it's overwritten in your vim configuration. |
@sangaline did you manage to solve this? Attached screenshot of my case Happens when I save the file |
I have this issue when used together with coc-prettier |
…reaks coc-eslint somehow) See also: neoclide/coc-eslint#16
Removing coc-prettier fixed the lag to me. |
Does anyone know how to change the timeout? Seems to be general issue that 0.5s is too short. |
Every time that I save a file I get this message:
If I save and quit, then I see this printed out in the terminal:
This is reproducible in even trivial files in empty projects, so I don't think the timeout is due to the complexity of the file being analyzed. Running
:CocCommand eslint.executeAutofix
manually works, but it can take 10-30 seconds on files with less than ten lines of code and no imports. Eslint works fine from the command-line without the same lag.I'm using version 1.1.2 of the plugin and eslint v5.16.0 on Linux. My coc-eslint config is completely vanilla, I haven't done anything except install the plugin. Please let me know if there's additional information that I can provide which would be helpful.
The text was updated successfully, but these errors were encountered: