mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
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.
52 lines
2.0 KiB
Python
Executable File
52 lines
2.0 KiB
Python
Executable File
#!/usr/bin/env python
|
|
"""Django's command-line utility for administrative tasks."""
|
|
|
|
import gc
|
|
import os
|
|
import sys
|
|
from pathlib import Path
|
|
|
|
# Add common/ to path so migration_utils module is importable (used by custom migrate command)
|
|
_common_path = str(Path(__file__).parent / "common")
|
|
if _common_path not in sys.path:
|
|
sys.path.insert(0, _common_path)
|
|
|
|
|
|
def main():
|
|
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "insights.settings")
|
|
try:
|
|
from django.core.management import execute_from_command_line
|
|
except ImportError as exc:
|
|
raise ImportError(
|
|
"Couldn't import Django. Are you sure it's installed and "
|
|
"available on your PYTHONPATH environment variable? Did you "
|
|
"forget to activate a virtual environment?"
|
|
) from exc
|
|
|
|
# Boot allocations are almost all permanent (modules, classes, registries), so cyclic GC
|
|
# during django.setup() only adds pauses (~300ms across ~470 collections). Disable it for
|
|
# the boot, then freeze the survivors so later full collections skip them too. Skipped when
|
|
# --settings/--pythonpath override the settings module, since those only take effect inside
|
|
# execute_from_command_line. See docs/internal/django-startup-time.md.
|
|
if not any(arg.startswith(("--settings", "--pythonpath")) for arg in sys.argv):
|
|
gc.disable()
|
|
try:
|
|
import django
|
|
|
|
django.setup()
|
|
finally:
|
|
gc.freeze()
|
|
gc.enable()
|
|
|
|
# Default query tags so management commands don't trip the DEBUG-only UntaggedQueryError
|
|
# in sync_execute. HTTP requests (runserver's CHQueries middleware) and Celery tasks reset
|
|
# tags at their own boundaries, so this only effectively applies to direct CLI commands.
|
|
from insights.datastore.query_tagging import Feature, Product, tags_context
|
|
|
|
with tags_context(product=Product.INTERNAL, feature=Feature.MANAGEMENT_COMMAND):
|
|
execute_from_command_line(sys.argv)
|
|
|
|
|
|
if __name__ == "__main__":
|
|
main()
|