Open ericnewkirk opened 3 years ago
I have seen this issue on CI testing and it is caused by the fact that we have enabled lint cache by default.
The current master branch has disabled it by default. We could try installing it from GitHub. The setting options(languageserver.lint_cache = FALSE)
may also work in the current CRAN release
Thanks @randy3k!
I added
options(languageserver.lint_cache = FALSE)
to my .RProfile before the language server is started and everything works again.
Ya, I only found the cause, but I couldn't understand why it fails. Even strangely, I observed this issue on Linux CI, not Windows.
Are you using the latest dev of lintr? Could you try using the latest dev?
> devtools::install_github("jimhester/lintr")
Skipping install of 'lintr' from a github remote, the SHA1 (387b939b) has not changed since last install.
Use `force = TRUE` to force installation
Suddenly linting has failed completely for me in vscode. I've tried several approaches to finding the source of the problem, but I can't reproduce it. This occurs in workspaces with and without a .RProject file or .lintr file, in all R files. The languageserver seems to fire up fine and other features such as hints on hover work fine. With extension debugging turned on the error in the output is:
I've dug through
callr
andprocessx
for clues but I don't see anything. I've also tried debugging in RStudio and found thatlintr
callsgzfile
via a long traceback in places, but I only see calls with"rb"
as the second argument. Even more strange, I can run the following in vscode and no error occurs:Here's some additional system info from languageserver startup in case there's anything there: