posit-dev / posit-dev/positron
Failed to connect to session's ZeroMQ Sockets: Provided sockets combination is not compatible
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 206
Description
System details:
Positron and OS details:
OS: Windows
Test ran in CI. See trace report.
Describe the issue:
R session failed to start up with this error:
Failed to connect to session's ZeroMQ Sockets: Provided sockets combination is not compatible
Nothing fancy happened in the test. It just attempted to start a R session and was greeted with the error. I've included screenshots to show the step by step behavior. The only odd things I noticed was the runtime list looking like it wasn't fully loaded before interacting and some notifications on bottom right containing errors.
Steps to reproduce the issue:
- Open Start a New Session menu
- Type in name of runtime and select it
- Verify runtime starts - FAIL
Expected or desired behavior:
Runtime should start w/o error.
Were there any error messages in the UI, Output panel, or Developer Tools console?
-
Failed to connect to session's ZeroMQ Sockets: Provided sockets combination is not compatible -
-
Logs are attached in the trace report.
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
Start with the linked Playwright trace report for the “validate can delete sessions” test and reproduce the Windows R-session startup failure. Trace the ZeroMQ socket connection path from the session-start flow. Done means the runtime starts successfully without the incompatible-sockets error and the affected test passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, typescript
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100