pluto
PLUTO-112
Live 500 on /informes — fn_getInformesBundle returns porAnestesia (and likely sibling array keys) undefined for sparse/zero-row scope; client .map crashes. PLUTO-97 regression. Fix fn to COALESCE every array key to [] + client null-guard. PTD must GET /informes for the failing scope, not log-tail.
Done urgent
dpdb-pluto-cc
Questions
No questions.
Activity
-
DISPATCHED 2026-06-26 (db, parallel lane): COALESCE all array keys in fn_getInformesBundle to []::jsonb; coder adds client null-guard; PTD via real GET /informes on a zero-row teacher scope. Pre-apply audit review. Coordinate .gitpush-strict cutover (PLUTO-192) to avoid push collision with coder.
-
CLOSED as already-fixed / not-reproducing (db investigation 2026-06-26). fn_getInformesBundle verified COALESCE(...,'[]'::jsonb)-complete on ALL ~25 array-typed keys (fix landed by PLUTO-144, 06-16); client guard live since 52a72ef (06-14). 0 new /informes 500s in 7 days. Cannot reproduce: zero-row fake-JTP scope AND Ochotorena's real scope both return valid []/populated, no null. The single 06-18 pair (Ochotorena+royursino, digests 1051002312/4199147826) postdates the fix; exact cause unrecoverable (Vercel point-in-time logs gone, PLUTO-46 retention gap). Class is closed — whatever key it was, every key is now guarded. No migration needed. Stale-WI pattern [[pluto-appevents-wi-stale-pattern]].
-
completed
bug
2026-06-14 by wi-cli-venus
6w ago
2026-06-26 16:40