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

17 lines
626 B
Python

"""Celery tasks for logs alerting.
The per-alert cap on non-event rows is enforced inline inside the Temporal
activity so the table stays bounded between cleanup runs. This module only hosts
the cold-path cleanup: pruning errored and state-transition rows older than their
retention window. That's slow-moving data, daily cadence is fine.
"""
from celery import shared_task
@shared_task(ignore_result=True, name="products.logs.backend.tasks.logs_alert_events_cleanup_task")
def logs_alert_events_cleanup_task() -> None:
from products.logs.backend.models import LogsAlertEvent
LogsAlertEvent.clean_up_old_events()