Support cross-host R sessions with sess
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- r, typescript
- Domain
- cli, developer-experience, tooling
Research direction
The issue mentions the new 'sess' architecture using bidirectional JSON-RPC over a stream socket. Start by examining the sess implementation in the codebase, likely in the src/ directory, to understand the current transport mechanism. Look for socket handling and connection logic. The goal is to modify sess to accept connections from a different host, possibly via TCP. Testing will involve setting up a cross-host scenario, perhaps with SSH forwarding, to verify the session attachment works.
Written by the indexing model from the issue text.
Description
There have been repeated requests to attach vscode-R to an R session running on a different host from the VS Code extension host, particularly in HPC environments where VS Code runs on a login node while R runs on a scheduler-allocated compute node.
Related issues include #469, #1019, #1047, #1276, #1359, #1391, #1506, and #1541.
Historically this was difficult because the session watcher depended on shared files, file watchers, and local process IDs.
With the new sess architecture, communication is now bidirectional JSON-RPC over a stream socket.
This should make cross-host sessions feasible in the future, for example through SSH socket forwarding or an additional TCP transport, without changing the higher-level session protocol.
I don't think vscode-R needs to manage SSH, Slurm, or other schedulers itself.
The useful boundary would be simply allowing sess to connect when the R process and the extension host are on different machines.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 139
- Avg merge
- 16h 16m
- Merged PRs (30d)
- 11
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from REditorSupport/vscode-R
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
REditorSupport/vscode-R#1687 · 4 comments · 3 reactions ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 65/100
REditorSupport/vscode-R#1756 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
REditorSupport/vscode-R#1755 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
REditorSupport/vscode-R#1751 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
REditorSupport/vscode-R#1749 · 5 comments · 3 reactions ·
All issues in REditorSupport/vscode-R
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
bcgov/bc-wallet-mobile#4761 · 1 comment ·
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100