quarto-dev / quarto-dev/quarto-cli

Multiple pdf format fail with generated figures

Open
#8,367 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug latex
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, r
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.