posit-dev / posit-dev/positron
"No state found" error for runtime session after extension host restart
Open
Nobody has claimed this yet.
area: core
area: runtimes
bug
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 206
Description
Positron Version:
Positron 2024.05.0 (Universal) build 1313
Steps to reproduce the issue:
This is a problem still leftover from #2683
- Open any folder in Positron (do not open a workspace file; the folder must not contain a Workspace file)
- Start R and/or Python
- From the File menu, choose "Save Workspace As"
- Save the workspace to any file name
Every once in a while, you see this error:
No state found for session 'r-c35e91d9' of runtime R 4.4.0
What did you expect to happen?
This is not a reproducible error; it only happens every once in a while.
Were there any error messages in the output or Developer Tools console?
From Window output:
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 by reviewing the linked renderer.log and the issue history for #2683, then reproduce the intermittent failure around saving a workspace after the extension host or runtime session restarts. The fix is complete when saving the workspace no longer reports that no state was found for the active R or Python session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, r, typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100