quarto-dev / quarto-dev/quarto
Execute in REPL hangs with larger Julia packages
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
Since upgrading to Julia 1.9 I've noticed that the Execute in REPL command (either by using the "run cell" button or one of the keyboard shortcuts) hangs indefinitely. I suspected it was compilation time, but whenever running a standalone .jl file, or a REPL initiated manually, this doesn't happen. This is confirmed by the fact that cells with more than a few lines that don't contain import statements hang too.
This MWE should reproduce the error:
---
title: "MWE"
---
```{julia}
using DifferentialEquations, Plots
# Rest of the cell never gets executed
```
I've noticed:
- The task manager shows a Julia process that uses CPU resources constantly while the command is executing
- The
executeInREPLcommand provided by the Julia VScode extension doesn't seem to have this problem. i.e running the same code in the interactive REPL from a.jlfile doesn't present the same problem - The prompt in the REPL changes. It doesn't say
julia>anymore, it shows some number. For instance#87using DifferentialEquations
I'm running version v1.85.0 of the Quarto VSCode extension, version v1.38.2 of the julia VSCode extension, and running on MacOS
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
Start with the Quarto VSCode extension's Execute in REPL path and compare it with the Julia VSCode extension's executeInREPL command. Reproduce the supplied MWE and inspect the altered REPL prompt and continuously active Julia process; done means larger Julia cells, including imports, execute without hanging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia, macos, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100