quarto-dev / quarto-dev/quarto-cli

Multiple pdf format fail with generated figures

Aperta
#8,367 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

bug latex
Lingua principale
JavaScript
Stelle
6k
Fork
458
Merge medio
1g 9h
PR unite (30g)
41

Descrizione

Bug description

When you have multiple pdf formats in a Quarto document that contains figures (generated by R for example), the process cleans up those figures after rendering the first PDF and the second PDF fails to render.

Steps to reproduce
---
title: "Test"
format: 
  pdf: default
  pdf+option: default
---

```{r}
cars |> 
  ggplot2::ggplot(ggplot2::aes(x = speed, y = dist)) +
  ggplot2::geom_line()
```
Expected behavior

The figures should be kept until all formats are rendered.

Actual behavior

The figures are deleted after the first PDF is rendered.

Your environment
  • IDE: RStudio Version 2023.12.0+369 (2023.12.0+369)
  • MacOS Sonoma 14.2.1
Quarto check output

Quarto 1.4.545
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.1.11: OK
Dart Sass version 1.69.5: OK
Deno version 1.37.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.4.545
Path: /Applications/quarto/bin

[✓] Checking tools....................OK
TinyTeX: v2023.12
Chromium: 869685

[✓] Checking LaTeX....................OK
Using: TinyTex
Path: /Users/admin/Library/TinyTeX/bin/universal-darwin
Version: 2023

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

[✓] Checking Python 3 installation....OK
Version: 3.11.4 (Conda)
Path: /opt/homebrew/Caskroom/miniconda/base/bin/python
Jupyter: 5.3.1
Kernels: python3

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

[✓] Checking R installation...........OK
Version: 4.3.2
Path: /Library/Frameworks/R.framework/Resources
LibPaths:
- /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/library
knitr: 1.45
rmarkdown: 2.25

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

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Use the minimal Quarto document in the reproduction, with two PDF formats and an R/ggplot2 figure, as the entry point. Trace rendering and cleanup across both PDF passes; done means both PDFs render successfully without the generated figure files being removed too early, with a regression check if the project provides one.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
javascript, r
Ambito
build-system
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.