R session not attached after run command `create terminal` and restart vscode

[liutiming]

Describe the bug
R session not attached after run command create terminal and restart vscode

To Reproduce
Steps to reproduce the behavior:

1. Connect to a cluster via SSH -
2. Configure setting turn on session watcher
3. Restart VSCode
4. Create terminal command
5. still shows R: (not attached)
6. Click on the R: (not attached) will run .vsc.attach() but nothing happens.

Do you want to fix by self? (I hope your help!)

Yes / No

Undecided as I am not sure what I can do

Expected behavior
R session attached and I can use functions like View(). Also, I hope that .vsc.attach() can work in a self-created R terminal. Right now my workflow is to use bjobs to open an interactive bash session and then run R so that I have the RAM that I need for large data analysis.

Screenshots

Environment (please complete the following information):

• OS: Ubuntu 16.04 (server). PC: Windows 10
• VSCode Version: 1.47.3
• R Version: 3.6.1
• vscode-R version: 1.4.4

[renkun-ken]

How do you connect to remote server?

It won't work if you simply ssh to your remote server in vscode terminal and start R there. Session watcher should work under Remote Development via SSH in this case.

If you are using Remote-SSH, and you need self-managed R sessions, please take a look at https://github.com/Ikuyadeu/vscode-R/wiki/R-Session-watcher#advanced-usage-for-self-managed-r-sessions, and make sure that the R session is started from the vscode workspace folder as the working directory.

[liutiming]

Thanks for so prompt reply! I am using remote SSH extension by vscode but it is not working yet as R is not attached

[renkun-ken]

It looks like it still does not work if you use Create terminal command. Then something is wrong with the file watcher.

Please Toggle Developer Tools, and you can see the extension logging is showing up in the developer console pane.

You could copy/paste the log here or simple save as the log and upload it here. Thanks!

[renkun-ken]

Also, would you like to run ls.str(.vsc) in a newly created R session and share the output here. A normal should be

> ls.str(.vsc)
attach : function ()  
browser : function (url, title = url, ..., viewer = getOption("vsc.browser", "Active"))  
capture_str : function (object)  
dataview : function (x, title, viewer = getOption("vsc.view", "Two"))  
dataview_data_type : function (x)  
dataview_table : function (data)  
dir_extension :  chr "/home/renkun/.vscode-R"
dir_session :  chr "/tmp/RtmpyNoqNY/vscode-R"
get_timestamp : function ()  
globalenv_file :  chr "/tmp/RtmpyNoqNY/vscode-R/globalenv.json"
globalenv_lock_file :  chr "/tmp/RtmpyNoqNY/vscode-R/globalenv.lock"
homedir :  chr "/home/renkun"
page_viewer : function (url, title = NULL, ..., viewer = getOption("vsc.page_viewer", 
    "Active"))  
pid :  int 129323
rebind : function (sym, value, ns)  
request : function (command, ...)  
request_file :  chr "/home/renkun/.vscode-R/request.log"
request_lock_file :  chr "/home/renkun/.vscode-R/request.lock"
show_globalenv :  logi TRUE
show_plot :  logi FALSE
show_view :  logi TRUE
tempdir :  chr "/tmp/RtmpyNoqNY"
unbox : function (x)  
update_globalenv : function (...)  
viewer : function (url, title = NULL, ..., viewer = getOption("vsc.viewer", "Two"))  
wd :  chr "/home/renkun/Workspaces/testR"
webview : function (url, title, ..., viewer)

[liutiming]

hope it helps!

attach : function ()  
browser : function (url, title = url, ..., viewer = getOption("vsc.browser", "Active"))  
capture_str : function (object)  
check_null_dev : function ()  
dataview : function (x, title, viewer = getOption("vsc.view", "Two"))  
dataview_data_type : function (x)  
dataview_table : function (data)  
dir_extension :  chr "/nfs/users/nfs_t/tl11/.vscode-R"
dir_plot_history :  chr "/tmp/RtmpYpHJBW/vscode-R/images"
dir_session :  chr "/tmp/RtmpYpHJBW/vscode-R"
get_timestamp : function ()  
globalenv_file :  chr "/tmp/RtmpYpHJBW/vscode-R/globalenv.json"
globalenv_lock_file :  chr "/tmp/RtmpYpHJBW/vscode-R/globalenv.lock"
homedir :  chr "/nfs/users/nfs_t/tl11"
new_plot : function ()  
null_dev_id :  Named int 2
null_dev_size :  num [1:2] 10.1 10.1
page_viewer : function (url, title = NULL, ..., viewer = getOption("vsc.page_viewer", 
    "Active"))  
pid :  int 29391
plot_file :  chr "/tmp/RtmpYpHJBW/vscode-R/plot.png"
plot_history_file :  NULL
plot_lock_file :  chr "/tmp/RtmpYpHJBW/vscode-R/plot.lock"
plot_updated :  logi FALSE
rebind : function (sym, value, ns)  
request : function (command, ...)  
request_file :  chr "/nfs/users/nfs_t/tl11/.vscode-R/request.log"
request_lock_file :  chr "/nfs/users/nfs_t/tl11/.vscode-R/request.lock"
show_globalenv :  logi TRUE
show_plot :  logi TRUE
show_view :  logi TRUE
tempdir :  chr "/tmp/RtmpYpHJBW"
unbox : function (x)  
update_globalenv : function (...)  
update_plot : function (...)  
viewer : function (url, title = NULL, ..., viewer = getOption("vsc.viewer", "Two"))  
wd :  chr "/lustre/scratch119/realdata/mdt2/teams/martin/users/tl11/w3"
webview : function (url, title, ..., viewer)  

[renkun-ken]

The log says "Ignored request outside workspace". Looks like your R session is started from /lustre/scratch119/realdata/mdt2/teams/martin/users/tl11/w3 which is outside your workspace folder open in VSCode.

Are you starting your R session from your workspace folder?

[liutiming]

ah interesting. the folder realdata does not actually exists and may be created by the cluster for task management. I will ask the tech support and get back to you

[GiulioGenova]

I had the same problem. I was using a workspace that was in a symlink, using the original directory solved the problem! Hope this helps

[TTTPOB]

I had the same problem. I was using a workspace that was in a symlink, using the original directory solved the problem! Hope this helps

after wasting 6 hours and now its 1:11 am, i finally find why i cannot get the r session connected

[renkun-ken]

Please try the build from #827.

[ddzhang3]

How do you connect to remote server?

It won't work if you simply ssh to your remote server in vscode terminal and start R there. Session watcher should work under Remote Development via SSH in this case.

If you are using Remote-SSH, and you need self-managed R sessions, please take a look at https://github.com/Ikuyadeu/vscode-R/wiki/R-Session-watcher#advanced-usage-for-self-managed-r-sessions, and make sure that the R session is started from the vscode workspace folder as the working directory.

It successfully work if I follow the steps. when I use Remote-SSH and start R session from the vscode terminal (even in the conda environment), the tag under the vscode window show R:(with session ID). But when I switch to another node with simply ssh command, the R session watcher did not work any more. Thanks for clarifying