zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
1.9 KiB
Insights Node.js services
Node.js services for Insights: ingestion pipeline, CDP, session recording, and more.
Running tests
Tests run against dedicated test databases, never the dev stack's databases:
| Store | Test database | Dev database (never used by tests) |
|---|---|---|
| Postgres (common) | test_insights |
insights |
| Postgres (persons) | test_persons |
insights_persons |
| Postgres (behavioral cohorts) | test_behavioral_cohorts |
behavioral_cohorts |
| Postgres (cyclotron) | test_cyclotron, test_cyclotron_node |
cyclotron |
| Datastore | insights_test |
default |
These are the defaults whenever NODE_ENV=test, which jest.setup-env.ts forces for every jest run. The schema is owned by Django and rust migrations, so the test databases must be created before the first run:
# From the repo root, with the dev stack's Postgres/Datastore/Kafka/Redis running:
pnpm --filter=@hanzo/nodejs setup:test
This runs Django's setup_test_environment (creates test_insights and the Datastore insights_test schema) plus the rust migrations for the persons, behavioral cohorts, and cyclotron test databases. Then:
cd nodejs
pnpm test # full suite (sharded in CI)
pnpm jest tests/path/to.test.ts # single file
Destructive test helpers refuse to run against a database without test in its name — see tests/helpers/database-guard.ts. The guard's error message explains how to fix a misconfigured environment.