posit-dev / posit-dev/positron
Shutting down the R session should gracefully shutdown the Reticulate session
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 206
Description
Currently, if we:
- Start the reticulate session
- Shutdown the R session
- Get an error message with:
Connection to server got closed. Server will not be restarted.
This happens because ending the R process will endupt shutting down child IPykernel which in turn is running the LSP server. When that connection is interrupted, the LSP client raises the message we see.
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.
Research direction
Reproduce the sequence of starting reticulate, shutting down the R session, and observing the child IPykernel and LSP connection. Trace the shutdown path across the R session, reticulate session, IPykernel, and LSP client to identify where orderly cleanup belongs. Done means shutting down R also stops the related sessions without the connection-closed error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, r
- Domain
- backend, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100