Render crashes when a proof, remark or solution block has an id that is not a cross-reference id
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- Mezza giornata
- Idoneità per principianti
- 72/100
Direzione di ricerca
Start by reading parseblockreftargets.lua at the reported failing line and trace how proof, remark, and solution IDs are handled; then inspect crossref/index.lua at its reported nil table index. Reproduce with the supplied Quarto document using both #my-proof and #myproof IDs in HTML, then check that each renders as an unnumbered block retaining its ID.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
A proof, remark or solution block that carries an id crashes the render when the id is not one of the cross-reference prefixes (prf-, rem-, sol-).
It fails in HTML and in Typst.
A theorem block such as ::: {#my-thm .theorem} with the same kind of id renders fine.
The error depends on the id:
- With a hyphen, such as
#my-proof,refTypereturnsmy, which is not a cross-reference category, soparseblockreftargets.luaindexes a nil category. - Without a hyphen, such as
#myproof, the block reachesadd_crossrefwith no category, andcrossref/index.luauses a nil table index.
I came across this while working on something else, and narrowed it down to the small example below.
Steps to reproduce
---
title: "Proof with an id"
format: html
---
::: {#my-proof .proof}
A proof with an id.
:::
Then run quarto render.
Replacing #my-proof with #myproof gives the second error.
Actual behavior
With #my-proof:
.../resources/filters/./quarto-pre/parseblockreftargets.lua:44: attempt to index a nil value (field '?')
With #myproof:
.../resources/filters/./crossref/index.lua:48: table index is nil
Expected behavior
The block renders as an unnumbered proof that keeps its id, as it does without an id.
Your environment
- IDE: none, command line.
- OS: macOS 27.0.
Quarto check output
Reproduced with a development build of main at 4c7b5d25d.
Quarto 99.9.9
[✓] Checking environment information...
Quarto cache location: /Users/mcanouil/Library/Caches/quarto
Project: none found (single-file mode)
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.10.0: OK
Dart Sass version 1.101.0: OK
Deno version 2.7.14: OK
Typst version 0.15.1: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 99.9.9
commit: 4c7b5d25da9e3f4197289b29ec579a440d15f692
Path: /Users/mcanouil/Projects/quarto-dev/quarto-cli/package/dist/bin
[✓] Checking tools....................OK
TinyTeX: v2026.07
Chrome Headless Shell: (not installed)
VeraPDF: (not installed)
[✓] Checking LaTeX....................OK
Using: TinyTex
Path: /Users/mcanouil/Library/TinyTeX/bin/universal-darwin
Version: 2026
[✓] Checking Chrome Headless....................OK
Using: Chrome from QUARTO_CHROMIUM
Path: /Applications/Brave Browser.app/Contents/MacOS/Brave Browser
[✓] Checking basic markdown render....OK
ℹ R version 4.6.1 (2026-06-24)
! Config '~/.Rprofile' was loaded!
[✓] Checking R installation...........OK
Version: 4.6.1
Path: /Library/Frameworks/R.framework/Versions/4.6/Resources
LibPaths:
- /Users/mcanouil/Library/R/arm64/4.6/library
- /Library/Frameworks/R.framework/Versions/4.6/Resources/library
knitr: 1.51
rmarkdown: 2.31
[✓] Checking Knitr engine render......OK
[✓] Checking Python 3 installation....OK
Version: 3.14.7
Path: /Users/mcanouil/Projects/quarto-dev/quarto-cli/tests/.venv/bin/python3
Jupyter: 5.9.1
Kernels: julia-1.12, python3
[IPKernelApp] WARNING | Kernel is running over TCP without encryption. All communication (including code and outputs) is sent in plain text and is susceptible to eavesdropping. Use IPC transport or launch with kernel manager-provisioned CurveZMQ keys to enable transport encryption.
[✓] Checking Jupyter engine render....OK
[✓] Checking Julia installation...
- Lingua principale
- JavaScript
- Stelle
- 6.1k
- Fork
- 478
- Merge medio
- 17h 36m
- PR unite (30g)
- 139
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di quarto-dev/quarto-cli
-
enhancement good-first-issue localization
Difficoltà 2/5 1-2 giorni Idoneità per principianti 76/100
quarto-dev/quarto-cli#15289 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug engines-jupyter
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
quarto-dev/quarto-cli#15281 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement localization
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
quarto-dev/quarto-cli#15268 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
html maintenance
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
quarto-dev/quarto-cli#15261 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement websites
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
quarto-dev/quarto-cli#15255 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di quarto-dev/quarto-cli
Issue simili
-
needs-area-label
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 2 giorni
-
serienstream.toApertaN: AdGuard for Windows P2: High T: Annoyance
Difficoltà 2/5 1-3 ore Idoneità per principianti 61/100
AdguardTeam/AdguardFilters#246310 ·
I maintainer di solito rispondono entro 1 giorno
-
Website: the hero tip's video play() has no catch, so a refused play is an unhandled rejectionAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
liberation-data/drivine#615 ·
I maintainer di solito rispondono entro 1 giorno
-
bug dependencies known-issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
unreleased dependencies
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
cloudfour/eslint-config#760 ·
I maintainer di solito rispondono entro 1 giorno