Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#278 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
html
Ambito
content

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
HTML
Stelle
136
Fork
199
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di RunestoneInteractive/thinkcspy

Tutte le issue di RunestoneInteractive/thinkcspy

Issue simili

Altre issue su Content

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.