REditorSupport / REditorSupport/vscode-R
Installing packages from source fails when enable LSP support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 139
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 5
Description
Describe the bug
When enable LSP support, multiple R-backend processes will exist. Then when I try to install some package from source, it will fail and print that the previous package can not be removed.
And in windows 11, when I kill these processes in the system manager, the installation will be succeed.
Also when I disable the LSP support in the setting, the installation also passes.
To Reproduce
I use the following task configuration in vscode.
{
"version": "2.0.0",
"tasks": [
{
"type": "R",
"code": [
"devtools::install(upgrade=FALSE, quick=TRUE)"
],
"group": {
"kind": "build",
"isDefault": true
},
"problemMatcher": [],
"label": "R: Quick Install",
"presentation": {
"reveal": "silent",
"focus": true,
"panel": "shared"
}
},
{
"type": "R",
"code": [
"devtools::install(upgrade=FALSE)"
],
"group": {
"kind": "build"
},
"problemMatcher": [],
"label": "R: Full Install",
"presentation": {
"reveal": "silent",
"focus": true,
"panel": "shared"
}
},
{
"type": "R",
"code": [
"devtools::build()"
],
"group": "build",
"problemMatcher": [],
"label": "R: Build"
}
]
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the supplied VS Code task configuration, with LSP support enabled and disabled, and compare the Windows process behavior. Confirm whether the package installation fails because an R-backend process keeps the previous package in use. Done means source installation succeeds with LSP enabled without manually killing processes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100