[Bug] /tree-of-knowledge calls GET /api/activity/progress anonymously → 401 console error (class of #312) #343

New Issue

2026-07-03T18:08:51Z

spikerj commented

2026-07-03 18:08:51 +00:00

Found by the P1 anonymous walk after tightening the console-error assertion (#314, epic #307).

Symptom

Visiting /tree-of-knowledge signed out fires GET /api/activity/progress, which 401s. The component catch-handles it into its empty state (the page renders fine), but Chromium logs the failed request as a console error — flaky in the walk because the fetch races the spec's assertions.

Root cause

tree-of-knowledge.component.ts#ngOnInit fetches personal progress unconditionally. /tree-of-knowledge is a public route, but the progress endpoint (correctly) requires auth. Same class as #312, except here the endpoint should stay authenticated — anonymous visitors simply have no progress to fetch.

Fix

Gate the fetch on keycloak.authenticated (the app's established pattern — see ACTIVITY_AUTH_GATE wiring in main.ts) and land directly on the existing empty state.

Found by the P1 anonymous walk after tightening the console-error assertion (#314, epic #307). ## Symptom Visiting `/tree-of-knowledge` signed out fires `GET /api/activity/progress`, which 401s. The component catch-handles it into its empty state (the page renders fine), but Chromium logs the failed request as a console error — flaky in the walk because the fetch races the spec's assertions. ## Root cause `tree-of-knowledge.component.ts#ngOnInit` fetches personal progress unconditionally. `/tree-of-knowledge` is a public route, but the progress endpoint (correctly) requires auth. Same class as #312, except here the endpoint *should* stay authenticated — anonymous visitors simply have no progress to fetch. ## Fix Gate the fetch on `keycloak.authenticated` (the app's established pattern — see `ACTIVITY_AUTH_GATE` wiring in `main.ts`) and land directly on the existing empty state.

spikerj added the bug label 2026-07-03 18:09:00 +00:00

spikerj commented

2026-07-03 19:39:34 +00:00

Resolved in spikersoft-angular PR #106 (merged to master). The progress fetch is now gated on keycloak.authenticated (ACTIVITY_AUTH_GATE pattern); anonymous visitors land on the existing empty state, and a new unit spec covers the anonymous path. Closing.

Resolved in spikersoft-angular PR #106 (merged to `master`). The progress fetch is now gated on `keycloak.authenticated` (ACTIVITY_AUTH_GATE pattern); anonymous visitors land on the existing empty state, and a new unit spec covers the anonymous path. Closing.

spikerj closed this issue

2026-07-03 19:39:40 +00:00

spikerj referenced this issue

2026-07-03 19:39:52 +00:00

[E2E P1] Anonymous walk — every public route + primary actions #314

spikerj referenced this issue

2026-07-03 20:03:37 +00:00

[Epic] Full-coverage Playwright E2E walk of the Angular app with live Jaeger + Seq telemetry #307

spikerj referenced this issue

2026-07-17 05:23:13 +00:00

[Backend][Tests] Five strict-mock tests carry no explicit assertion (SonarQube S2699 BLOCKER x6 — 5 fixed, 1 false-positived) #636

Sign in to join this conversation.