Render crashes when a proof, remark or solution block has an id that is not a cross-reference id
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- Ein halber Tag
- Anfängerfreundlichkeit
- 72/100
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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...
- Vorherrschende Sprache
- JavaScript
- Sterne
- 6.1k
- Forks
- 478
- Ø Merge
- 17 Std. 53 Min.
- Gemergte PRs (30 T.)
- 135
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus quarto-dev/quarto-cli
-
accessibility bug embed
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 85/100
quarto-dev/quarto-cli#15306 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bootstrap bug themes
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
quarto-dev/quarto-cli#15304 ·
Maintainer antworten meist innerhalb von 1 Tag
-
accessibility bug code-blocks html themes
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
quarto-dev/quarto-cli#15303 ·
Maintainer antworten meist innerhalb von 1 Tag
-
accessibility brand bug dark-mode
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
quarto-dev/quarto-cli#15301 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bootstrap bug html tables
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
quarto-dev/quarto-cli#15300 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in quarto-dev/quarto-cli
Ähnliche Issues
-
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 87/100
OWASP/CheatSheetSeries#2905 ·
Maintainer antworten meist innerhalb von 1 Tag
-
desktop enhancement P2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 74/100
AllTheMods/ATM10-Aeronautics#159 ·
Maintainer antworten meist innerhalb von 6 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
ComposioHQ/composio#5249 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
zilliztech/memsearch#838 ·
Maintainer antworten meist innerhalb von 1 Tag