Luacheck linter stops working after some time. #51
Labels
Comments
|
I can confirm. Cant reliably reproduce but it does happen
…On Wed, Dec 19, 2018, 1:11 AM AuahDark ***@***.*** wrote:
It's usually happends at 10-20 minutes of coding session, then Luacheck
errors/warnings stops displayed. The only way to show it back is to reload
VS Code window.
Reproducing this is bit hard, but I notice it happends faster when I have
to work & switch to multiple files.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#51>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ANUy4Blpkjz1kHEe1H-lgfjYdESq8GYGks5u6diggaJpZM4ZZmmG>
.
|
|
@MikuAuahDark Can you provide the detail log by enable the |
|
Okay I'll try tomorrow. |
|
Okay here's the log (version 2.2.5) Notice the last few log where Luacheck only runs at ~2ms. That's where Luacheck linter stopped working. |
liwangqian
added a commit
that referenced
this issue
Feb 15, 2019
|
Problem still exist in 2.2.9 |
|
Still exist as of v2.2.10 |
|
I've encountered exactly the same problem, and found that the extension tried to execute |
|
@updateing I seem can't reproduce the corrupted server/providers/diagnostic-provider.js _run(linter, input) {
return new Promise((resolve, reject) => {
/*重新创建一个检查进程*/
this.coder.tracer.info(`luacheck executable ${linter.cmd}`);
let proc = execFile(linter.cmd, linter.args, { cwd: linter.cwd }, (error, stdout, stderr) => {
if (error != null) {
reject({ error: error, stdout: stdout, stderr: stderr });
} else {
resolve({ error: error, stdout: stdout, stderr: stderr });
}
});
proc.stdin.end(input);
});
}So the problem probably lies in |
|
Okay it looks like the Is it possible to fix this? |
|
This can also happen with UNC paths inside of WSL |
|
[Info - 17:25:11] Connection to server got closed. Server will restart. Error: write EOF |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's usually happends at 10-20 minutes of coding session, then Luacheck errors/warnings stops displayed. The only way to show it back is to reload VS Code window.
Reproducing this is bit hard, but I notice it happends faster when I have to work & switch to multiple files.
The text was updated successfully, but these errors were encountered: