Files
zeekay 1b367e2b62 chore: rebase the tree onto upstream master
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.
2026-08-01 15:44:40 -07:00

35 lines
2.3 KiB
INI

[pytest]
pythonpath = . common tools/insightscli-commands tools/owners tools/query-performance-ai
env =
DEBUG=1
TEST=1
DJANGO_SETTINGS_MODULE = insights.settings
# Trunk flaky-test detection wants per-test file paths in junit XML; the default
# xunit2 family strips the file/line testcase attributes.
junit_family = xunit1
# --pytest-durations=0 disables the pytest-durations plugin by default; CI shard steps re-enable it explicitly
# -p no:tach disables tach's pytest plugin: without --tach it builds the full import graph (~5-10s
# per invocation) only to print a "could be skipped" hint. Opt back in with: pytest -p tach --tach
# -p no:langsmith_plugin skips the langsmith pytest plugin (auto-registered by a transitive dependency,
# ~0.8s of imports per invocation); nothing in this repo uses langsmith's pytest integration.
# Note: the pytest11 entry point name is "langsmith_plugin" (module langsmith.pytest_plugin), not
# "langsmith", so `-p no:langsmith` silently fails to match anything and the plugin still loads.
# -p no:faker skips faker's auto-registered pytest plugin (~75ms of imports per invocation);
# nothing in this repo uses the `faker` fixture or the library (faker is a transitive dep)
# -p pytest_boot_gc opens the boot GC window (gc.disable) before pytest-django runs
# django.setup(), which happens before conftest files load; the root conftest closes it
addopts = -p no:warnings -p no:tach -p no:langsmith_plugin -p no:faker -p pytest_boot_gc --reuse-db --pytest-durations=0 --ignore=insights/user_scripts --ignore=services/llm-gateway --ignore=services/stripe-mock --ignore=common/ingestion/acceptance_tests --ignore=tools/insightscli --ignore=tools/insightscli-commands --ignore=tools/owners --ignore=tools/traffic-sim --ignore=tools/query-performance-ai --ignore=products/desktop
markers =
ee
datastore_only
skip_on_multitenancy
async_migrations
requires_secrets: test needs internal secrets or infra and is skipped on external PRs
quarantine: applied automatically to tests quarantined via .test_quarantine.json (insightscli test:quarantine)
persons_db_direct: test exercises the persons DB directly and must not have the personinsights fake / ORM block active
asyncio_mode = auto
asyncio_default_fixture_loop_scope = module
asyncio_default_test_loop_scope = module