REditorSupport / REditorSupport/vscode-R

Lintr error in Rmd and Qmd files

Open
#1,419 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
1.2k
Forks
139
Avg merge
2h 46m
Merged PRs (30d)
5

Description

Describe the bug
When opening a Rmd template, lintr does not work and shows the following error:

failed to  run diagnostics: ! in callr subprocess. caused by error: ! linter 'object_length_linter' failed in : path[1]="": no such file or directory

To Reproduce
Steps to reproduce the behavior:

  1. Open Rmarkdown
  2. reprex minimal (or any other template)

Can you fix this issue by yourself? (We appreciate the help)

No

// R path for Linux
"r.rterm.linux": "~/miniconda3/bin/radian",

Screenshots
With error lens enabled:

image

  • OS: vUbuntu 22.04.3 LTS
  • VSCode Version: 1.82.1
  • R Version: 4.3.1
  • vscode-R version: [e.g. 1.2.2]

Additional context
I installed the latest dev version of languageserver via

install.packages("languageserver", repos = c(
    reditorsupport = "https://reditorsupport.r-universe.dev",
    getOption("repos")
))

which did not help.

Also lintr itself works fine, in .R files, but also in when manually calling it

image

I found a related topic https://github.com/REditorSupport/vscode-R/issues/1198. However, this topic is supposed to be fixed with a new language server.

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure when opening an Rmarkdown or Quarto template in VS Code, then compare diagnostics with an .R file and with lintr run manually. Investigate the interaction between the vscode-R extension, languageserver, and lintr; done means Rmd and Qmd files produce diagnostics without the missing-path error.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown, r, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.