mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 20:42:43 +00:00
* Revert "revert: roll source tree back to v1.4.0 to restore production"
This reverts commit e444a90b10.
* fix(v1.4.2): summaries.WEIGHT + medications array guards + healthcheck IPv4
Three production bugs surfaced after the v1.4.0 deploy stabilized:
1. `TypeError: undefined is not an object (evaluating 'E?.summaries.WEIGHT')`
on /dashboard and /insights for users without weight readings —
the optional chain stopped at `data` when it needed to also cover
`data.summaries`. Fixed: `data?.summaries?.WEIGHT` (one level deeper).
2. `TypeError: y?.filter is not a function` on /medications — the
medications query value was non-array (likely a stale
service-worker response from an older API shape). Replaced with
`Array.isArray(medications) ? medications : []` so the page is
immune to any future shape drift.
3. Healthcheck-induced 503 outage (already in 1.4.1 — included here
so 1.4.2 is the single coherent release). The docker-compose
healthcheck used `localhost` which busybox-wget resolves to IPv6
::1; Next.js standalone listens on IPv4 0.0.0.0 only. Pinned
to 127.0.0.1.
This release also includes everything from v1.4.1 (which never
published a clean GHCR tag): the per-section admin extraction, the
testcontainers integration suite, the Playwright + axe-core E2E
foundation, the moodLog SSRF fix, the central error-redaction in
WideEventBuilder + Glitchtip, the medical-citation drift fixes
(ESH 2023, Saint-Maurice attribution, steps source), and the docs
sync.
Co-Authored-By: Marc-André Bombeck <mbombeck@gmail.com>
58 lines
2.0 KiB
TypeScript
58 lines
2.0 KiB
TypeScript
/**
|
|
* Vitest globalSetup — boots ONE Postgres testcontainer for the whole
|
|
* integration run, applies migrations, and exposes the connection URL
|
|
* via process.env.DATABASE_URL. The teardown returned at the end stops
|
|
* the container after all test files have finished.
|
|
*
|
|
* Why globalSetup instead of beforeAll/afterAll per file:
|
|
* - The application's Prisma singleton in `src/lib/db.ts` is built at
|
|
* module load time using the current `process.env.DATABASE_URL`. If
|
|
* the container is rotated between test files, the singleton keeps
|
|
* pointing at the dead container and queries fail. Booting once,
|
|
* keeping the URL stable, and truncating between tests is both
|
|
* faster and safer.
|
|
* - Truncate-between-tests still gives per-test isolation; see
|
|
* `setup.ts -> truncateAllTables`.
|
|
*/
|
|
import { execSync } from "node:child_process";
|
|
import { dirname, resolve } from "node:path";
|
|
import { fileURLToPath } from "node:url";
|
|
|
|
import {
|
|
PostgreSqlContainer,
|
|
type StartedPostgreSqlContainer,
|
|
} from "@testcontainers/postgresql";
|
|
|
|
const __filename = fileURLToPath(import.meta.url);
|
|
const __dirname = dirname(__filename);
|
|
const PROJECT_ROOT = resolve(__dirname, "..", "..");
|
|
|
|
let container: StartedPostgreSqlContainer | null = null;
|
|
|
|
export default async function setup(): Promise<() => Promise<void>> {
|
|
container = await new PostgreSqlContainer("postgres:16-alpine")
|
|
.withDatabase("healthlog_test")
|
|
.withUsername("healthlog")
|
|
.withPassword("healthlog")
|
|
.start();
|
|
|
|
const url = container.getConnectionUri() + "?schema=public&pgbouncer=false";
|
|
process.env.DATABASE_URL = url;
|
|
|
|
// Provided so child processes (e.g. Prisma's CLI) inherit the URL.
|
|
// Vitest also forwards process.env to test workers, so the
|
|
// application Prisma singleton sees this URL when it loads.
|
|
execSync("pnpm db:migrate:deploy", {
|
|
cwd: PROJECT_ROOT,
|
|
stdio: "inherit",
|
|
env: { ...process.env, DATABASE_URL: url },
|
|
});
|
|
|
|
return async () => {
|
|
if (container) {
|
|
await container.stop({ remove: true });
|
|
container = null;
|
|
}
|
|
};
|
|
}
|