RunestoneInteractive / RunestoneInteractive/thinkcspy

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

Open
#278 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug help wanted
Dominant language
HTML
Stars
135
Forks
197
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
content
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.