Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
R session not attached after run command `create terminal` and restart vscode
See original GitHub issueDescribe the bug
R session not attached after run command create terminal and restart vscode
To Reproduce Steps to reproduce the behavior:
- Connect to a cluster via SSH -
- Configure setting turn on session watcher
- Restart VSCode
- Create terminal command
- still shows
R: (not attached) - 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
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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
Please try the build from #827.