Inability to Attach active R terminal on Compute Nodes in HPC Environment

[XZhangGit]

Describe the bug
When launching an active R terminal on a compute node within an HPC environment and attempting to attach it using .vsc.attach(), the terminal remains detached with the message "R: (not attached)" displayed. Clicking to attach does not initiate the attachment process. However, on the login node, the active R terminal automatically attaches as expected, likely due to the configuration in ~/.Rprofile. I found a similar issue reported by another user (https://stackoverflow.com/questions/73087813/how-do-i-make-sure-my-r-session-attached-is-using-the-compute-node-instead-of-th), where he mentioned "my data viewer wouldn't be attached and I couldn't view my data in the 'workspace'.", and there hasn't been a solution provided yet.

To Reproduce
Steps to reproduce the behavior:

1. Launch an interactive R on the compute node on HPC.
2. Run .vsc.attach() in R.
3. Observe the terminal displaying "R: (not attached)" without successfully attaching.

**Can you fix this issue by yourself? **
No

Please attach setting.json

"r.alwaysUseActiveTerminal": true,
"r.bracketedPaste": true,
"r.sessionWatcher": true,
"r.rterm.option": [],
"r.rterm.linux": "/path/to/radian",

Expected behavior
The terminal should attach successfully to the interactive R session on the compute node when .vsc.attach() is called, similar to the behavior observed on the login node where it attaches automatically.

Screenshots
Terminal showing "R: (not attached)" when attempting to attach after running .vsc.attach():

Terminal automatically attached on the login node due to ~/.Rprofile configuration:

Environment (please complete the following information):

• OS: [Linux]
• VSCode Version: [1.90.2]
• R Version: [4.3.1]
• REditorSupport version: [2.8.4]

Thank you!

[hariesramdhani]

Can also confirm that I encountered the same bug, thanks for raising the issue!

[krferrier]

I am experiencing the same bug and would love a solution. I have no problem attaching an R-session from a login node, but can't attach an R session from an interactive compute node. The option to start an R Terminal works as well, but it uses a login node by default. I haven't been able to figure out why exactly the compute nodes are unable to see/use rlanguageserver options, nor how to modify the R Terminal to be initiated with a non-login node.