Bug: C# Hello World lesson - grading error due to browser compilation conflict #214

New Issue

2026-05-26T17:40:37Z

Zhekrom commented

2026-05-26 17:40:37 +00:00

Title: Bug: C# Hello World lesson - grading error due to browser compilation conflict
Severity: High
Mode: C# lessons section � Hello World lesson grading
Lesson ID / File: C# Hello World lesson
Environment: Firefox (any version), Windows (any version)
Date/Time: May 26, 2026

Source Code
(Not applicable � UI / workflow bug)

Steps to Reproduce
1. Navigate to the C# Hello World lesson
2. Complete the exercise
3. Attempt to submit / get graded
4. Observe the error message

Expected Output
The submission should be graded and the result displayed.

Actual Output
The following error is shown:
"Error: Este intento se cargó desde el servidor, pero «Compilar en el navegador» está activado. Haz clic en «Nuevo intento» para regenerar una versión calificada localmente y envía de nuevo."

The user is blocked from completing the lesson.

Suggested Priority
High � blocks the grading workflow, which is a core part of the learning experience. Users cannot complete the lesson.

Additional Notes
�� BUG ��
The error indicates a state mismatch: the attempt was loaded from the server but the UI has "Compile in browser" mode enabled. The user shouldn't need to understand this internal state to complete a lesson.

�� UX SUGGESTION ��
Beyond the bug itself, the overall flow is confusing for beginners. The error message is technical and hard to understand for someone who just started learning programming. Suggested improvements:
- Show a clearer, beginner-friendly message that explains what to do in simple terms
- Ideally, handle the state mismatch automatically so the user doesn't have to click "New attempt"
- The lesson interface should guide the user naturally through what needs to be done, so they focus on learning instead of figuring out how the UI works
- Inexperienced users often give up when faced with confusing technical errors like this one

Title: Bug: C# Hello World lesson - grading error due to browser compilation conflict Severity: High Mode: C# lessons section � Hello World lesson grading Lesson ID / File: C# Hello World lesson Environment: Firefox (any version), Windows (any version) Date/Time: May 26, 2026 Source Code (Not applicable � UI / workflow bug) Steps to Reproduce 1. Navigate to the C# Hello World lesson 2. Complete the exercise 3. Attempt to submit / get graded 4. Observe the error message Expected Output The submission should be graded and the result displayed. Actual Output The following error is shown: "Error: Este intento se cargó desde el servidor, pero «Compilar en el navegador» está activado. Haz clic en «Nuevo intento» para regenerar una versión calificada localmente y envía de nuevo." The user is blocked from completing the lesson. Suggested Priority High � blocks the grading workflow, which is a core part of the learning experience. Users cannot complete the lesson. Additional Notes �� BUG �� The error indicates a state mismatch: the attempt was loaded from the server but the UI has "Compile in browser" mode enabled. The user shouldn't need to understand this internal state to complete a lesson. �� UX SUGGESTION �� Beyond the bug itself, the overall flow is confusing for beginners. The error message is technical and hard to understand for someone who just started learning programming. Suggested improvements: - Show a clearer, beginner-friendly message that explains what to do in simple terms - Ideally, handle the state mismatch automatically so the user doesn't have to click "New attempt" - The lesson interface should guide the user naturally through what needs to be done, so they focus on learning instead of figuring out how the UI works - Inexperienced users often give up when faced with confusing technical errors like this one

Screenshot 2026-05-26 134253.png

144 KiB

Zhekrom changed title from ~~Bug: Hello World lesson - grading error due to browser compilation conflict~~ to Bug: C# Hello World lesson - grading error due to browser compilation conflict

2026-05-26 17:41:50 +00:00

spikerj commented

2026-06-10 06:58:37 +00:00

Fix up in spikerj/spikersoft-angular#38.

Root cause: the grading router picked the execution path purely from the current "In-browser compile" state. If the attempt was issued by the server (toggle off at load time, or the WASM runtime fell back to a server-cached attempt — likely on Firefox) but the toggle was on at submit time, the browser had no local grading state for that attempt token and blocked the submit with the technical error you saw.

Fix (per the UX suggestion — handled automatically now):

The submit self-heals: it first tries to restore local grading state from the offline cache; otherwise, when online, it sends the submission to the server, which still holds that attempt's tests — no "New attempt" click needed, the student just gets graded.
The error can now only appear when offline with nothing recoverable, and it was reworded in beginner-friendly terms (en + es): it tells the student plainly that the exercise can't be graded offline and to start a new attempt.

Regression tests cover all four routing branches. Will close when the PR merges.

Fix up in spikerj/spikersoft-angular#38. **Root cause:** the grading router picked the execution path purely from the current "In-browser compile" state. If the attempt was issued by the server (toggle off at load time, or the WASM runtime fell back to a server-cached attempt — likely on Firefox) but the toggle was on at submit time, the browser had no local grading state for that attempt token and blocked the submit with the technical error you saw. **Fix (per the UX suggestion — handled automatically now):** - The submit self-heals: it first tries to restore local grading state from the offline cache; otherwise, when online, it sends the submission to the server, which still holds that attempt's tests — no "New attempt" click needed, the student just gets graded. - The error can now only appear when offline with nothing recoverable, and it was reworded in beginner-friendly terms (en + es): it tells the student plainly that the exercise can't be graded offline and to start a new attempt. Regression tests cover all four routing branches. Will close when the PR merges.

spikerj closed this issue

2026-06-10 07:11:30 +00:00

spikerj referenced this issue

2026-07-12 01:01:31 +00:00

[Bug][Prod] GameServer rejects ALL player JWTs — audience config 'spikersoft-api' vs Keycloak's actual 'account' (regression from #407 hardening) #491

spikerj referenced this issue

2026-07-12 01:07:34 +00:00

[Bug][Prod] GameServer rejects ALL player JWTs — audience config 'spikersoft-api' vs Keycloak's actual 'account' (regression from #407 hardening) #491

spikerj referenced this issue

2026-07-16 23:51:28 +00:00

Blueprint diagram: connection wires broken on Angular 22 — rete-angular-plugin injects removed ComponentFactoryResolver (flaky e2e tools-walk failure) #622

spikerj referenced this issue