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.
53 lines
1.9 KiB
Python
53 lines
1.9 KiB
Python
from __future__ import annotations
|
|
|
|
import os
|
|
from datetime import datetime
|
|
from uuid import UUID
|
|
|
|
from django.db.models import Q
|
|
|
|
from products.alerts.backend.scheduling import (
|
|
advance_next_check_at,
|
|
compute_shard_offset_seconds as shared_compute_shard_offset_seconds,
|
|
)
|
|
|
|
__all__ = [
|
|
"MAX_BYTES_TO_READ",
|
|
"SCHEDULE_INTERVAL_SECONDS",
|
|
"advance_next_check_at",
|
|
"compute_shard_offset_seconds",
|
|
"due_alerts_q",
|
|
]
|
|
|
|
# How often the Temporal schedule fires. Drives shard granularity in
|
|
# `compute_shard_offset_seconds`: schedule fires every N seconds, so a
|
|
# cadence of M seconds has `M // N` shard slots available.
|
|
SCHEDULE_INTERVAL_SECONDS = 60
|
|
|
|
# Per-query CH read cap (bytes). Cohort chunking (`MAX_ALERT_COHORT_SIZE`) keeps reads
|
|
# bounded at the source; this is the safety net if a chunk surprises us. Tunable via env
|
|
# so we can bump for customers whose filters genuinely need more headroom without
|
|
# redeploying. Aligns to CH's GiB-based reporting (1024^3) so the value here matches
|
|
# the "max bytes: N GiB" in CH error messages. Default 5 GiB (5,368,709,120).
|
|
# Lives here, not in `temporal/constants.py`, because `alert_check_query.py` (the
|
|
# consumer) is outside the temporal package. Importing it from temporal would create
|
|
# a circular import via `temporal/__init__.py` to activities to alert_check_query.
|
|
MAX_BYTES_TO_READ = int(os.environ.get("LOGS_ALERTING_MAX_BYTES_TO_READ", "5368709120"))
|
|
|
|
|
|
def compute_shard_offset_seconds(alert_id: UUID, check_interval_minutes: int) -> int:
|
|
return shared_compute_shard_offset_seconds(
|
|
alert_id,
|
|
check_interval_minutes,
|
|
schedule_interval_seconds=SCHEDULE_INTERVAL_SECONDS,
|
|
)
|
|
|
|
|
|
def due_alerts_q(now: datetime, *, broken_state: str, snoozed_state: str) -> Q:
|
|
return (
|
|
Q(enabled=True)
|
|
& (Q(next_check_at__lte=now) | Q(next_check_at__isnull=True))
|
|
& ~Q(state=broken_state)
|
|
& ~Q(state=snoozed_state, snooze_until__gt=now)
|
|
)
|