cannot attach session when workspace is under symbolic link

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to ‘…’
2. Click on ‘…’
3. Scroll down to ‘…’
4. See error

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

Yes / No

(If yes,) what kind of help do you want? (e.g. Which file should I fix, Survey (related documents)

(If related)setting.json

// R.exe path for windows
"r.rterm.windows": "",

// R path for Mac OS X
"r.rterm.mac": "/usr/local/bin/R",

// R path for Linux
"r.rterm.linux": "/usr/bin/R",

// R command line options (i.e: --vanilla)
"r.rterm.option": [],

// An optional encoding to pass to R when executing the file, i.e. 'source(FILE, encoding=ENCODING)'
"r.source.encoding": "UTF-8",

// Keeping focus when running
"r.source.focus": "editor",

// Use active terminal for all commands, rather than creating a new R terminal
"r.alwaysUseActiveTerminal": false,

// Use bracketed paste mode
"r.bracketedPaste": false,

// Enable R session watcher (experimental)
"r.sessionWatcher": false,

// Delay in milliseconds before sending each line to rterm (only applies if r.bracketedPaste is false)
"r.rtermSendDelay": 8,

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem. You can show the keybord contents by pressing F1 and Developer: toggle screencast mode

Environment (please complete the following information):

• OS: [e.g. Windows, macOS, Linux]
• VSCode Version: [e.g. 1.42.0]
• R Version: [e.g. 3.6.2]
• vscode-R version: [e.g. 1.2.2]

Additional context Add any other context about the problem here.

[renkun-ken]

I could reproduce this. It is caused by R’s getwd() will follow the symlink, which is inconsistent with the workspace folder in vscode. We check whether the R’s working directory is consistent with the vscode workspace folder, and it is likely that multiple vscode instances are open with different workspace folders, we need to ensure that only the vscode instance with the correct workspace folder open should attach the session.

Looks like we could always follow the symlink of workspace folders on vscode side and check whether they match the R cwd.

[renkun-ken]

Please try the build from #827.