Suggested Priority
Critical � the core functionality of all C# lessons is completely down. Users cannot execute any code, which makes the interactive learning path unusable.
Additional Notes
The 500 error is a server-side error, likely an unhandled exception in the CSharpCodeRunner API backend (ASP.NET Core). The issue does not appear to be client-side or related to the specific code written � it happens consistently with any custom code.
Title: Bug: Execute code in sandbox returns 500 error
Severity: Critical
Mode: C# lessons � code sandbox / code runner
Lesson ID / File: All C# lessons � CSharpCodeRunner API endpoint
Environment: Firefox (any version), Windows (any version)
Date/Time: May 26, 2026
Source Code
(Not applicable � backend API issue)
Steps to Reproduce
1. Navigate to any C# lesson
2. Write custom C# code in the editor
3. Click the execute / run button
4. Observe the error
Expected Output
The code should be sent to the sandbox, compiled, executed, and the result displayed in the UI.
Actual Output
The following error is displayed: "Error: Http failure response for https://api.spikersoft.com/api/CSharpCodeRunner/run: 500 OK"
Suggested Priority
Critical � the core functionality of all C# lessons is completely down. Users cannot execute any code, which makes the interactive learning path unusable.
Additional Notes
The 500 error is a server-side error, likely an unhandled exception in the CSharpCodeRunner API backend (ASP.NET Core). The issue does not appear to be client-side or related to the specific code written � it happens consistently with any custom code.
Root cause: CSharpCodeRunnerController.Run/RunLesson converted every exception (including validator ArgumentException for syntax errors and CodeExecutionSecurityException for forbidden constructs) into HTTP 500, so any custom code with a typo or a blocked namespace returned 500 OK instead of a useful message.
Fix in spikerj/spikersoft-backend#2 — validation/security failures now return 400 with the actual compile/security message; genuine infrastructure faults still return 500. Regression tests added.
Root cause: `CSharpCodeRunnerController.Run`/`RunLesson` converted every exception (including validator `ArgumentException` for syntax errors and `CodeExecutionSecurityException` for forbidden constructs) into HTTP 500, so any custom code with a typo or a blocked namespace returned `500 OK` instead of a useful message.
Fix in spikerj/spikersoft-backend#2 — validation/security failures now return `400` with the actual compile/security message; genuine infrastructure faults still return `500`. Regression tests added.
Closing as fixed by spikerj/spikersoft-backend#2.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Title: Bug: Execute code in sandbox returns 500 error
Severity: Critical
Mode: C# lessons � code sandbox / code runner
Lesson ID / File: All C# lessons � CSharpCodeRunner API endpoint
Environment: Firefox (any version), Windows (any version)
Date/Time: May 26, 2026
Source Code
(Not applicable � backend API issue)
Steps to Reproduce
1. Navigate to any C# lesson
2. Write custom C# code in the editor
3. Click the execute / run button
4. Observe the error
Expected Output
The code should be sent to the sandbox, compiled, executed, and the result displayed in the UI.
Actual Output
The following error is displayed: "Error: Http failure response for https://api.spikersoft.com/api/CSharpCodeRunner/run: 500 OK"
Suggested Priority
Critical � the core functionality of all C# lessons is completely down. Users cannot execute any code, which makes the interactive learning path unusable.
Additional Notes
The 500 error is a server-side error, likely an unhandled exception in the CSharpCodeRunner API backend (ASP.NET Core). The issue does not appear to be client-side or related to the specific code written � it happens consistently with any custom code.
Root cause:
CSharpCodeRunnerController.Run/RunLessonconverted every exception (including validatorArgumentExceptionfor syntax errors andCodeExecutionSecurityExceptionfor forbidden constructs) into HTTP 500, so any custom code with a typo or a blocked namespace returned500 OKinstead of a useful message.Fix in spikerj/spikersoft-backend#2 — validation/security failures now return
400with the actual compile/security message; genuine infrastructure faults still return500. Regression tests added.Closing as fixed by spikerj/spikersoft-backend#2.