## [Bug] SQL Playground Returns 404 Error When Accessed from Integration Tests #192

New Issue

2026-05-24T16:10:33Z

enjin2310 commented

2026-05-24 16:10:33 +00:00

🧩 Summary

Attempting to open the SQL Playground from the Pruebas de Integración (Unity Tests) section results in a 404 Page Not Found error. The page fails to load and displays the message “La página que buscas no existe o puede haberse movido.”

🧪 Steps to Reproduce

Navigate to Pruebas de Integración (Unity Tests).
Click on Abrir Playground SQL.
Observe that the browser redirects to learn.spikersoft.com/tools/sql-playground.
The page displays a 404 error instead of loading the SQL Playground interface.

✅ Expected Behavior

The SQL Playground should open normally, allowing users to run SQL queries and integration tests.

❌ Actual Behavior

The page fails to load and shows a 404 error, indicating that the resource is missing or misrouted.

📸 Evidence

The attached screenshot shows the error message:

“Página no encontrada — La página que buscas no existe o puede haberse movido.”

🧠 Possible Root Cause

Broken or outdated route reference in the Unity Tests module.
SQL Playground endpoint (/tools/sql-playground) may have been renamed or removed.
Incorrect path mapping in the navigation or router configuration.

🔧 Suggested Fix

Verify the route configuration for the SQL Playground in the Unity Tests module.
Update the link to the correct endpoint (e.g., /tools/playground/sql or /tools/sql).
Add a redirect rule for legacy URLs to prevent future 404 errors.

🌐 Environment

URL: learn.spikersoft.com/tools/sql-playground
Version: v2026.05.22b
Browser: Firefox (latest)
OS: Windows 10.0
User: Jorge (logged in)

### 🧩 Summary Attempting to open the **SQL Playground** from the **Pruebas de Integración (Unity Tests)** section results in a **404 Page Not Found** error. The page fails to load and displays the message “La página que buscas no existe o puede haberse movido.” ### 🧪 Steps to Reproduce 1. Navigate to **Pruebas de Integración (Unity Tests)**. 2. Click on **Abrir Playground SQL**. 3. Observe that the browser redirects to `learn.spikersoft.com/tools/sql-playground`. 4. The page displays a **404 error** instead of loading the SQL Playground interface. ### ✅ Expected Behavior The SQL Playground should open normally, allowing users to run SQL queries and integration tests. ### ❌ Actual Behavior The page fails to load and shows a **404 error**, indicating that the resource is missing or misrouted. ### 📸 Evidence The attached screenshot shows the error message: > “Página no encontrada — La página que buscas no existe o puede haberse movido.” ### 🧠 Possible Root Cause - Broken or outdated route reference in the **Unity Tests** module. - SQL Playground endpoint (`/tools/sql-playground`) may have been renamed or removed. - Incorrect path mapping in the navigation or router configuration. ### 🔧 Suggested Fix 1. Verify the route configuration for the SQL Playground in the **Unity Tests** module. 2. Update the link to the correct endpoint (e.g., `/tools/playground/sql` or `/tools/sql`). 3. Add a redirect rule for legacy URLs to prevent future 404 errors. ### 🌐 Environment - **URL:** learn.spikersoft.com/tools/sql-playground - **Version:** v2026.05.22b - **Browser:** Firefox (latest) - **OS:** Windows 10.0 - **User:** Jorge (logged in)

Screenshot 2026-05-24 120830.png

105 KiB

spikerj commented

2026-06-15 04:04:41 +00:00

Root cause found: the Abrir playground SQL action targets the secondary tools router outlet (/tools/(tools:sql-playground)), but the coding-topic template bound that string straight to [routerLink]. When routerLink is given a string, Angular treats it as plain path segments and never parses the (outlet:path) auxiliary-outlet grouping — so it resolved to a non-existent route and 404'd. The i18n link data itself was already correct.

Fixed in spikersoft-angular PR #48 by navigating these actions with router.navigateByUrl() (which parses the full outlet URL, matching how the menu bar already opens this playground). Will close once that PR merges.

Root cause found: the *Abrir playground SQL* action targets the secondary `tools` router outlet (`/tools/(tools:sql-playground)`), but the coding-topic template bound that string straight to `[routerLink]`. When `routerLink` is given a string, Angular treats it as plain path segments and never parses the `(outlet:path)` auxiliary-outlet grouping — so it resolved to a non-existent route and 404'd. The i18n link data itself was already correct. Fixed in `spikersoft-angular` PR #48 by navigating these actions with `router.navigateByUrl()` (which parses the full outlet URL, matching how the menu bar already opens this playground). Will close once that PR merges.

spikerj commented

2026-06-15 05:28:18 +00:00

Resolved in spikersoft-angular PR #48 (merged to master). Coding-topic action links now navigate via router.navigateByUrl, which correctly resolves the secondary tools-outlet URL, so Abrir playground SQL opens the SQL Playground instead of returning a 404. Closing.

Resolved in `spikersoft-angular` PR #48 (merged to `master`). Coding-topic action links now navigate via `router.navigateByUrl`, which correctly resolves the secondary `tools`-outlet URL, so **Abrir playground SQL** opens the SQL Playground instead of returning a 404. Closing.

spikerj closed this issue

2026-06-15 05:28:30 +00:00

spikerj referenced this issue

2026-07-09 01:14:35 +00:00

backend: expand integration coverage — art pipe messaging, safety RPC, GPU leases, quiz path #465

spikerj referenced this issue

2026-07-15 20:09:53 +00:00

[Security][CI] OpenBao Phase 1: Gitea Actions secrets → AppRole fetch; rotate the committed runner token (epic #543) #545

spikerj referenced this issue

2026-07-15 20:22:28 +00:00

[Security][CI] OpenBao Phase 1: Gitea Actions secrets → AppRole fetch; rotate the committed runner token (epic #543) #545

spikerj referenced this issue