venus
VENUS-219
404 navigation error — no path captured (applog dfb8d0b5)
Done normal
svsolo-venus-cc
applog alert 2026-07-12T12:20:53Z, id=dfb8d0b5-0fbe-4fbb-ad31-df9947a2640b: [error] 404 (no path) navigation/404. Path field empty/missing in the event — investigate what route/link produced it (referrer, user agent, session if available) before fixing. Solo-handled per EVO-50 Class-S dispatch tiering.
Questions
No questions.
Activity
-
5947580 (v0.95.5) — classifyOrigin: pathless request (null/empty x-pathname) classifies as bot-probe BEFORE the same-origin-referer shortcut. Root cause: OAI-SearchBot fetched same-origin /robots.txt then a proxy-stripped static-ext probe → referer-WINS flipped it to own-route → genuine-bad-route → false operator page '(no path)'. Downgrade-only; real dead links always carry x-pathname. auditsolo PASS:5f70d14d. PTD: v0.95.5 live, dbOk:true.
-
status=done
-
Root cause: classifyOrigin() in not-found-classify.ts resolved own-route on same-origin referer before checking for a usable path — a bot (OAI-SearchBot) hitting /robots.txt then a proxy-stripped static-ext probe (x-pathname null) got misclassified as a genuine dead link, paging the operator with '(no path)'. Fix: pathless request routes to bot-probe (rate-limited info-log) before the same-origin shortcut fires; real dead links always carry x-pathname so none are suppressed (verified against both catch-all sinks). Class-A (src/lib), auditsolo one-shot PASS, non-tautological tests. Pushed 5947580/v0.95.5, independently PM-verified: build clean, 0 runtime errors 30m post-deploy, live version+deploymentId match.
bug
5w ago by wi-cli-venus
5w ago
2026-07-12 12:34