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

Temporary Runestone exercise would only render in HTML, never in static output forms

Abierto
  • ¿Algo no está bien?
#278 6 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
html
Área
content

Línea de trabajo

Start by inspecting checkpoints 2.10.1 and 2.11.1 on the linked published page and identify their source content. Compare HTML rendering with the static output forms and update the exercise authoring to supported PreTeXt syntax. Done means both checkpoints render correctly in every supported output form.

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

Descripción

bug help wanted

Please check the current issues Many bug reports are duplicates, this just creates more work for us. Searching the issues first may give you your answer or a workaround! If not adding new information to an existing report is much more helpful than a new report.

What Course are you in
Knowing the course will help us a lot

idahostateuniversity_httlacs_spring26

What Page were you on

https://runestone.academy/ns/books/published/idahostateuniversity_httlacs_spring26/simple-python-data_updating-variables.html

What is your username
norkish

Describe the bug
A clear and concise description of what what you were trying to accomplish and what went wrong. Vague statements like X does not work are not helpful. Imagine if one of your students sent you an email that said, "My program doesn't work, whats wrong with it?" Could you help them with only that to go on?

Checkpoints 2.10.1 and 2.11.1 read:

"There was once a (temporary) Runestone exercise here, which would only render in HTML output, and never in static output forms. That (temporary) device is no longer supported as of 2025-11-04, since the exercise should now be authored in supported PreTeXt syntax. You might alert the author to this situation."

Traceback
If you got here through the Bug Report page and there was a stack trace, please paste it here

Javascript Errors
Many many errors can be quickly diagnosed from the Javascript Console error log. On Chrome this is View --> Developer --> Javascript Console, on Safari ⌥⌘i or Develop --> Show Web Inspector on Firefox Tools --> Web Developer --> Toggle Tools

Lenguaje dominante
HTML
Estrellas
136
Forks
199
Sin PR fusionados en 30 d

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 RunestoneInteractive/thinkcspy

Todos los issues de RunestoneInteractive/thinkcspy

Issues similares

Más issues de Content

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.