[session-watcher] Fail to start on remote

Config:

• Startup with custom R interpreter and project based .Rprofile
• r.sessionwatcher enabled

# vscode
Sys.setenv(TERM_PROGRAM = "vscode")
source(file.path(Sys.getenv(if (.Platform$OS.type == "windows") "USERPROFILE" else "HOME"), ".vscode-R", "init.R"))

set in project root’s .Rprofile

I even added a cat() statement in ~/.vscode-R/init.R to track whether the code is being executed.

radian                                                                                                      
vscode session watcher: success
R version 3.6.1 (2019-07-05) -- "Action of the Toes"
Platform: x86_64-pc-linux-gnu (64-bit)

However, the R session is still not attached in vscode. The same happens outside of the project (i.e. without a custom .Rprofile).

Running “R: Create R Terminal” errors - but so quickly that I cannot see the reason. I also cannot find a log for this.

More info

• R_HOME = /opt/spack/opt/spack/linux-centos7-x86_64/gcc-9.2.0/r-3.6.1-j25wr6zcofibs2zfjwg37357rjj26lqb/rlib/R
• radian v0.4.4

[pat-s]

It’s sourced because I can see the {renv} header after startup. I am calling the vscode lines after source("renv/activate.R") in the workspace root .Rprofile - could this mess things up?

Also

Sys.getenv("TERM_PROGRAM")    
[1] "vscode"

but yeah - the custom cat() output I added to init.R is missing here - hence it is not being executed (correctly).

Calling source(file.path(Sys.getenv(if (.Platform$OS.type == "windows") "USERPROFILE" else "HOME"), ".vscode-R", "init.R")) after startup attaches the session.

-> Turns out I have to call the vscode lines before source("renv/activate.R")

Thanks for helping - turns out its not related to an issue on your side but looks like renv is getting into the way somehow.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.