Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report building fails when run from an rmarkdown or quarto document #7

Open
phuongquan opened this issue Nov 23, 2022 · 1 comment
Open
Labels
bug Something isn't working

Comments

@phuongquan
Copy link
Member

phuongquan commented Nov 23, 2022

When running daiquiri_report() or report_data() from an rmd/qmd file, get errors such as:

Duplicate chunk label 'unnamed-chunk-1'

or

Duplicate chunk label 'setup'

This appears to have started happening with version 1.0.2, which was updated to fix CRAN errors in Debian systems (6d5ddd7)

UPDATE: Version 1.0.3 partially solves this issue in that unlabelled chunks in a parent rmd/qmd file no longer cause an error, but a chunk labelled setup will still result in an error.

UPDATE: Version 1.1.1 now allows a chunk labelled setup in a parent rmd/qmd file without causing an error.

Current workarounds are:

  • in the parent rmd/qmd file, rename any chunks that are mentioned in the error with a unique label
  • in the parent rmd/qmd file, add options(knitr.duplicate.label = "allow") to a chunk at the top (see also https://bookdown.org/yihui/rmarkdown-cookbook/duplicate-label.html)
  • create reports from simple R scripts instead of rmd/qmd files
@phuongquan phuongquan added the bug Something isn't working label Nov 23, 2022
@phuongquan
Copy link
Member Author

@Analect is this the issue you were getting?

@phuongquan phuongquan pinned this issue Nov 23, 2022
phuongquan added a commit that referenced this issue Nov 24, 2022
…directory instead of setting intermediates_dir. See issue #7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant