spikerj/spikersoft-issues
1
0
Fork 0
Code Issues 196 Pull Requests Actions Packages Projects Releases Wiki Activity

JavaScript Playground: Start debugging runs lesson code after switching to sandbox #133

New Issue
Closed
opened 2026-05-13 12:17:12 +00:00 by spikerj · 1 comment
spikerj commented 2026-05-13 12:17:12 +00:00
Owner
Copy Link
Copy Source

Summary

When switching from Lessons mode to Sandbox mode and using Start debugging, the debugger executes code from the previous Lessons session instead of the code shown in the Sandbox editor.

Steps to reproduce

  1. Open the JavaScript Playground in Lessons mode with lesson code (e.g. console.log("Hello from JavaScript!");).
  2. Switch to Sandbox mode.
  3. Enter different sandbox code in the editor (e.g. var testing = 'hello';).
  4. Use Start debugging.
  5. Observe that output/execution reflects the lesson code (e.g. "Hello from JavaScript!") rather than the sandbox content.

Expected behavior

Start debugging should always run and debug the code that is currently active in the Sandbox editor after mode switch.

Actual behavior

Debugging appears to use a stale reference to Lessons mode code while the UI still shows the Sandbox editor contents.

Notes

Likely causes to investigate: shared state not cleared on mode switch, wrong buffer/source passed to the debugger runner, or the debugger binding to the lesson document instead of the sandbox document.

## Summary When switching from **Lessons** mode to **Sandbox** mode and using **Start debugging**, the debugger executes code from the **previous Lessons** session instead of the code shown in the Sandbox editor. ## Steps to reproduce 1. Open the JavaScript Playground in **Lessons** mode with lesson code (e.g. `console.log("Hello from JavaScript!");`). 2. Switch to **Sandbox** mode. 3. Enter different sandbox code in the editor (e.g. `var testing = 'hello';`). 4. Use **Start debugging**. 5. Observe that output/execution reflects the **lesson** code (e.g. `"Hello from JavaScript!"`) rather than the sandbox content. ## Expected behavior **Start debugging** should always run and debug the code that is currently active in the **Sandbox** editor after mode switch. ## Actual behavior Debugging appears to use a stale reference to **Lessons** mode code while the UI still shows the Sandbox editor contents. ## Notes Likely causes to investigate: shared state not cleared on mode switch, wrong buffer/source passed to the debugger runner, or the debugger binding to the lesson document instead of the sandbox document.
spikerj commented 2026-06-15 09:36:59 +00:00
Author
Owner
Copy Link
Copy Source

Root cause confirmed (matches the "wrong buffer/source passed to the debugger" hypothesis in the notes): the step-debugger's source provider read LanguageRunner.code (codeSignal). In advanced sandbox mode the editor binds to the active file (activeFileContent), not codeSignal, so codeSignal still held the prior lesson/beginner code — the debugger ran that stale source while the editor showed the sandbox content.

Fixed in spikersoft-angular PR #51 by pointing the provider at the mode-aware getSourceForChrome() (active file in advanced sandbox, codeSignal otherwise) — the same source the Run Code button already uses, so Run and Debug now execute identical, current editor content. Tests: 29/29 across the JS runner + step-debugger suites. Will close once PR #51 merges.

Root cause confirmed (matches the "wrong buffer/source passed to the debugger" hypothesis in the notes): the step-debugger's source provider read `LanguageRunner.code` (`codeSignal`). In advanced sandbox mode the editor binds to the active file (`activeFileContent`), not `codeSignal`, so `codeSignal` still held the prior lesson/beginner code — the debugger ran that stale source while the editor showed the sandbox content. Fixed in `spikersoft-angular` PR #51 by pointing the provider at the mode-aware `getSourceForChrome()` (active file in advanced sandbox, `codeSignal` otherwise) — the same source the Run Code button already uses, so Run and Debug now execute identical, current editor content. Tests: 29/29 across the JS runner + step-debugger suites. Will close once PR #51 merges.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#133