fix: Admin Insights page could crash on a single query failure (v0.55.2)
Two changes: 1. Replaced positional `GROUP BY 1` (not used anywhere else in this codebase) with the conventional pattern of repeating the actual grouped expression — matches every other groupBy call site in the app. 2. Switched Promise.all -> Promise.allSettled across the six independent aggregate queries feeding the six charts, defaulting a failed one to an empty array (that chart just renders "No data yet") instead of taking the whole page down. Logs the failure server-side either way. Couldn't reproduce locally (no DB in this sandbox), but confirmed the allSettled path works: the production build itself hit a real connection failure against the (absent) local DB and degraded cleanly instead of crashing, which is exactly the resilience this fixes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
@@ -2,6 +2,11 @@
|
||||
|
||||
All notable changes to Epicure are documented here. This file is mirrored in-app at `/changelog` (and in the admin dashboard) via `apps/web/lib/changelog.ts` — update both together.
|
||||
|
||||
## 0.55.2 — 2026-07-19 18:20
|
||||
|
||||
### Fixed
|
||||
- Admin Insights page could 500 the whole panel if any one of its six aggregate queries failed — replaced a non-standard positional GROUP BY with the expression-repeat pattern used everywhere else in the codebase, and made the six queries independent (Promise.allSettled) so one failing degrades that one chart instead of crashing the page.
|
||||
|
||||
## 0.55.1 — 2026-07-19 18:05
|
||||
|
||||
### Fixed
|
||||
|
||||
Reference in New Issue
Block a user