Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Computational figure filenames regress to positional auto-naming, losing Q1's label-based stability (knitr; Jupyter has the same gap unimplemented)

Cerrado
  • ¿Algo no está bien?
#741 1 comentario 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
rust
Área
build-system

Línea de trabajo

Start with the typst-testing/p8-orange-book-base fixture under crates/quarto/tests/smoke-all/typst/orange-book/ and reproduce the missing fig-cars-1.svg during q2 render. Trace how the label is handled for the knitr execution path and compare the expected label-derived filename with the observed positional name. Done means the fixture's cross-document figure reference resolves with a stable label-derived filename; the issue notes that work is already tracked in internal strand bd-2lxj10z0.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Summary

Computational figure filenames lose their label-based stability compared to Quarto 1.x. In Quarto 1.x, a labelled executable chunk's output filename is derived from the author's label: option — #| label: fig-cars on an R chunk yields fig-cars-1.svg; the same principle applies to Jupyter, which names outputs <label>-output-<n>.<ext> (e.g. fig-visualization-output-1.png). Different concatenation convention per engine, but in both cases the label, not the chunk's position in the document, determines the artifact's filename — which is what makes the name stable across edits (reordering sections, inserting a chunk earlier in the file, etc. doesn't change it).

In q2, the knitr chunk's label: option never reaches the engine — it's consumed upstream (to drive q2's own crossref numbering) and stripped from the code text before knitr ever executes it. knitr falls back to its generic positional default, the same name it would produce for an unlabelled chunk (unnamed-chunk-1-1.svg instead of fig-cars-1.svg), even though the chunk is labelled. Any file or document that references the artifact by its expected, label-derived name breaks.

Reproduction

chapter1.qmd:

```{r}
#| label: fig-cars
#| fig-cap: "A plot of the cars dataset"
plot(cars)


Another file in the same project hand-references the artifact chapter1 produces, exactly as Quarto 1.x would name it:

```markdown
![First appendix panel](chapter1_files/figure-typst/fig-cars-1.svg){#fig-appendix-panel-a}

Expected (matches quarto render, Quarto 1.x): chapter1.qmd execution produces chapter1_files/figure-typst/fig-cars-1.svg, and the reference above resolves.

Observed (q2 render): the same chunk instead produces chapter1_files/figure-typst/unnamed-chunk-1-1.svg. The hand-authored reference to fig-cars-1.svg now points at a file that doesn't exist, which fails at compile time (missing-image error) for any format that isn't forgiving about broken image links (e.g. Typst).

Found via the typst-testing/p8-orange-book-base smoke-all fixture (crates/quarto/tests/smoke-all/typst/orange-book/), which reuses the same figure across chapter2.qmd, appendix.qmd, and appendix-b.qmd by referencing it directly by its expected filename — a pattern Quarto 1.x's naming convention is specifically designed to support.

Why this matters beyond the immediate 404

Stable, label-derived artifact filenames are a real, relied-upon Quarto 1.x behavior — they let other documents, includes, and hand-authored references point at a generated artifact by a name that won't shift as the document changes. Falling back to positional auto-naming (unnamed-chunk-N) removes that guarantee silently: the render succeeds for the originating document and only breaks downstream, wherever something else references the artifact by name.

Tracking

Root-caused and being fixed via internal strand bd-2lxj10z0.

Lenguaje dominante
Rust
Estrellas
264
Forks
18
Merge medio
12 h 54 min
PR fusionados (30 d)
105

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de quarto-dev/q2

Todos los issues de quarto-dev/q2

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.