Running code line-by-line (Cntrl + Enter) feels extremely laggy in Positron (Slurm Posit WB)

[mislavzorko]

I have:

• searched the issue tracker for similar issues
• installed the latest version of Quarto CLI
• formatted my issue following the Bug Reports guide

Bug description

Hi, we are using Posit WB on AWS-deployed Slurm cluster.

Running R code line-by-line using Cntrl + Enter in Positron works normally in .R scripts, but when we try to run the code from RMarkdown / Quatro documents, it starts to lag heavily. It also produces bunch of temporary local .vdoc files.

At the same time, in RStudio, everything works normally.

Here is an example when run line-by-line.

> tictoc::tic()
> 1+1
[1] 2
> tictoc::toc()
4.84 sec elapsed

When we select the whole chunk, it works instantly.

> tictoc::tic()
+ 1+1
+ tictoc::toc()
[1] 2
0.002 sec elapsed

Any ideas on what we might try here?

Thanks

Steps to reproduce

No response

Actual behavior

No response

Expected behavior

No response

Your environment

No response

Quarto check output

Quarto 1.9.37
[✓] Checking environment information...
      Quarto cache location: /pfs/home/.cache/quarto
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.8.3: OK
      Dart Sass version 1.87.0: OK
      Deno version 2.4.5: OK
      Typst version 0.14.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.9.37
      Path: /usr/lib/rstudio-server/bin/quarto/bin

[✓] Checking tools....................OK
      TinyTeX: v2024.07.03
      Chromium: (not installed)
      Chrome Headless Shell: (not installed)
      VeraPDF: (not installed)

[✓] Checking LaTeX....................OK
      Using: TinyTex
      Path: /pfs/home/.TinyTeX/bin/x86_64-linux
      Version: 2024

[✓] Checking Chrome Headless....................OK
      Chrome:  (not detected)

[✓] Checking basic markdown render....OK

[✓] Checking R installation...........OK
      Version: 4.4.1
      Path: /opt/R/4.4.1/lib/R
      LibPaths:
        - /pfs/home/.cache/R/renv/sandbox/linux-ubuntu-jammy/R-4.4/x86_64-pc-linux-gnu/22bdb599
      knitr: 1.51
      rmarkdown: 2.31

[✓] Checking Knitr engine render......OK

[✓] Checking Python 3 installation....OK
      Version: 3.10.12
      Path: /usr/bin/python3
      Jupyter: (None)

      Jupyter is not available in this Python installation.
      Install with python3 -m pip install jupyter

[✓] Checking Julia installation...

[mcanouil]

This is an issue with the VSCode/Positron extension: https://github.com/quarto-dev/quarto

(Maintainers will transfert)

The "vdoc" are "virtual documents" as the native code formatting feature has to move/isolate code to allow various formatters to format it.
If you format on save and has limited environment, this can indeed feels laggy.

[mislavzorko]

Thanks so much for a quick reply. I realized this was cli repo as soon as I opened this issue, but didn't know there was a separate one for extension. Sorry for double work.

[mcanouil]

Mentioning a community extension for VSCode/Positron to format Quarto documents that might give you a better experience, it's called Panache.

• https://marketplace.visualstudio.com/items?itemName=jolars.panache

[mislavzorko]

Thanks for helping here @mcanouil.

I turned of any sort of formatting and I noticed that .vdoc files appear when Control + Click on some object.
Even with this features turned off, running code line-by-line is still very laggy.