Skip to content

Linting error doesn't update when coding #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

Closed
klesh opened this issue Sep 23, 2022 · 2 comments · Fixed by #25
Closed

Linting error doesn't update when coding #24

klesh opened this issue Sep 23, 2022 · 2 comments · Fixed by #25

Comments

@klesh
Copy link
Contributor

klesh commented Sep 23, 2022

Using nvim-lspconfig configuration on nvim 0.7.2 with golang 1.19

When renaming variables, the linting error doesn't seem to update, unless I reload the file:
image

@klesh
Copy link
Contributor Author

klesh commented Sep 24, 2022

saw sth in the debugging log, not sure if it was related:

[ERROR][2022-09-24 09:45:02] .../vim/lsp/rpc.lua:420	"rpc"	"golangci-lint-langserver"	"stderr"	"unexpected end of JSON input\n"
[ERROR][2022-09-24 09:45:51] .../vim/lsp/rpc.lua:420	"rpc"	"golangci-lint-langserver"	"stderr"	'2022/09/24 09:45:51 jsonrpc2 handler: notification "exit" handling error: jsonrpc2: code -32601 message: method not supported: exit\n'

I would try to fix the problem if someone could point me a direction 😄

@klesh
Copy link
Contributor Author

klesh commented Sep 24, 2022

after some digging, I managed to pinpoint the offending error:
image
which decoded to the follow error message by base64 -d:

level=warning msg="[runner] Can't run linter goanalysis_metalinter: goheader: open .golangci-goheader.template: no such file or directory"
level=error msg="Running error: 1 error occurred:\n\t* can't run linter goanalysis_metalinter: goheader: open .golangci-goheader.template: no such file or directory\n\n"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant