Problem report: https://runestone.academy/assignment/student/doAssignment?assignment_id=275187

[irunestone]

A problem was reported through the Runestone "Report a Problem" form.

Field	Value
Reporter	esfoell791
Email	esfoell791@stkate.edu
Course	st_kate_csjava_fall26
Page	https://runestone.academy/assignment/student/doAssignment?assignment_id=275187
Reported at	2026-09-14T01:17:51.802915

Description

The error was TypeError: can't access property "score", e is null
Status Code: 201
Detail: "none"

[bnmnetp]

Found it, and it is not the same code path everyone has been rebuilding.

Books built from the runestone PyPI package take their JavaScript from the legacy_support branch, not main. That branch's last commit is 2026-07-05, so it never received 13f36e9 (the #1393 fix, on main since 2026-08-18 and released in components 8.2.8). Rebuilding these books against the 8.2.x components does not reach this code at all.

The bug on legacy_support, in runestonebase.js:

post_return = await response.json();
let scoreSpec = post_return.detail;      // null for an ungraded event
...
if (gradeBox && !this.isTimed && scoreSpec.score) {   // TypeError: e is null

/logger/bookevent answers a successful ungraded save with 201 and detail: null. Reading .score off that null throws, and because the score-display update sits inside the same try that guards the fetch, the save's error handler catches it and tells the student their work was not saved — on work that was saved.

A 201 in the report is the tell. main cannot produce that alert with that status, so every one of these is a legacy-JS book: #1461, #1472, #1495 and this one. #1472 and #1508 are even the same course (st_kate_csjava_fall26), five days apart.

Fixed on legacy_support in 4b756c2 — a port of the main-branch fix: the score display moves out of the save's try, a null score spec is skipped, and response.status is no longer read when fetch itself rejected.

Verified by running main's runestonebase_logging.test.js against the legacy file: 7 pass after the fix, and 3 of them — including this exact case — fail on the file as it was, so the tests are really exercising it.

To reach students this needs a runestone release (7.13.8 → 7.13.9) and a rebuild of the affected RST books, which is a bigger lift than the PreTeXt rebuild already under way.