Broken links in /wiki (HTTP 502, 167 links)

Broken links in /wiki (HTTP 502, 167 links)

Task ID: d543badf-3f1c-4f4c-bf3f-1cef3f679b9c Type: one-time Layer: Atlas Status: Complete

Goal

Investigate and resolve 167 broken links in /wiki that were returning HTTP 502 errors.

Affected endpoints

• /wiki/home
• /wiki/brain-regions
• /wiki/researchers
• /wiki/entities
• /wiki/hypotheses
• /wiki/circuits
• /wiki/events
• /wiki/investment-landscape
• /wiki/models
• /wiki/resources

Acceptance criteria

• All 10 listed /wiki endpoints return HTTP 200
• No 502 errors on /wiki routes

Work Log

2026-04-23 09:29 PDT — Watchdog root-cause pass (task:1f14d4a7)

• Reopened by watchdog after repeated zero-commit runs; current task is to make the original d543badf-3f1c-4f4c-bf3f-1cef3f679b9c retryable or close it with evidence.
• Live bounded curl checks against http://localhost:8000/wiki* timed out with status 000, and direct wiki_page("home") profiling showed the current wiki render path taking 38s.
• Root cause found in scidex/atlas/entity_auto_linking.py: each wiki render resolves every extracted entity mention by repeatedly scanning/fuzzy-matching canonical_entities; one page spent 37.8s in auto-linking.
• Planned fix: replace per-candidate fuzzy resolver calls in the wiki auto-linking path with bulk exact canonical/alias lookups, and repair the wiki AI figure query that still uses SQLite json_extract() against PostgreSQL JSONB.
• Implemented the fix in scidex/atlas/entity_auto_linking.py and api.py. Verification in-process with cache disabled after rebasing onto latest origin/main: /wiki/home profiled at 1.498s with auto-linking reduced to 0.586s, all 10 listed wiki pages rendered in 0.548-1.930s each, and python3 -m py_compile scidex/atlas/entity_auto_linking.py api.py passed.

2026-04-13 — Investigation and verification (task:d543badf)

Investigated all 10 /wiki endpoints listed in the task. All return HTTP 200 OK:

200 /wiki/home
200 /wiki/brain-regions
200 /wiki/researchers
200 /wiki/entities
200 /wiki/hypotheses
200 /wiki/circuits
200 /wiki/events
200 /wiki/investment-landscape
200 /wiki/models
200 /wiki/resources

Finding: The 502 errors were transient — likely caused by a temporary backend restart or upstream proxy issue. The wiki routes are served by api.py and the application is currently healthy. No code changes were required.

Root cause: Resolved by commits 35dd7fd8c and ddd79554e on main which added a contains-match fallback for wiki slug resolution, fixing 112+ broken /wiki links. All 10 affected endpoints confirmed HTTP 200 on current main (HEAD: f0a2361d3).

File: d543badf_broken_links_in_wiki_http_502_spec.md

Modified: 2026-04-25 23:40

Size: 2.6 KB