quarto-dev / quarto-dev/quarto
VS Code Extension: Run All Cells causes disconnection from R interactive terminal
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
Bug description
On some documents, f I do quarto -> run all cells, the connection between the interactive R session and the terminal turns red and gets interrupted. This can also happen if I run each cell manually, but run several in a row. If I slowly send each one manually, it doesn't happen. It doesn't seem related to the contents of the cell, it can happen when I am defining a function and not running it. This happens on both a M1 and M2 Mac; it's been happening for months so it isn't related to any particular updates. I'm not sure how to even debug this issue, do you all have any suggestions? Thanks so much.
Steps to reproduce
I'm not sure how to reproduce it, but it happens fairly regularly.
Actual behavior
R session and terminal loses connection when running quarto -> run all cells, or otherwise sending several cells of input to the R process.
Expected behavior
The interactive session to just run normally.
Your environment
Both a M1 and M2 Mac. This happens both using Cursor and VS Code.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or specific entry points are named. Start by reproducing the failure in VS Code or Cursor with Quarto's Run All Cells and an R interactive terminal, then compare it with slowly sending cells manually. Done means the R session and terminal remain connected when several cells are sent in succession.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100