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.
56 lines
1.9 KiB
Python
56 lines
1.9 KiB
Python
# Keep in sync with frontend `BREAKPOINT_COLUMN_COUNTS.sm`.
|
|
DASHBOARD_GRID_COLUMN_COUNT = 12
|
|
|
|
# Hard cap on rows returned per widget query (run_widgets throttles + UI "25+" footer).
|
|
MAX_WIDGET_RESULT_LIMIT = 25
|
|
|
|
# Default when config omits limit — catalog/OpenAPI default, below the hard cap.
|
|
DEFAULT_WIDGET_LIST_LIMIT = 10
|
|
|
|
# Activity events list allows a larger page than other list widgets (lightweight rows).
|
|
ACTIVITY_EVENTS_MAX_LIMIT = 50
|
|
ACTIVITY_EVENTS_DEFAULT_LIMIT = 25
|
|
ACTIVITY_EVENTS_MAX_PROPERTY_FILTERS = 20
|
|
ACTIVITY_EVENTS_MAX_PROPERTY_FILTER_VALUES = 100
|
|
ACTIVITY_EVENTS_MAX_PROPERTY_KEY_LENGTH = 400
|
|
ACTIVITY_EVENTS_MAX_PROPERTY_LABEL_LENGTH = 400
|
|
ACTIVITY_EVENTS_MAX_PROPERTY_VALUE_LENGTH = 4000
|
|
|
|
# Logs list allows the largest page — log rows are cheap and users scan many at once.
|
|
LOGS_LIST_MAX_LIMIT = 100
|
|
LOGS_LIST_DEFAULT_LIMIT = 50
|
|
|
|
# Cap widgets per batch create / run-widgets request.
|
|
MAX_WIDGETS_BATCH_SIZE = 10
|
|
|
|
# Upper bound on pinned recordings pulled from a collection to scope a session replay widget. Bounds the
|
|
# session_ids IN clause sent to Datastore and the Python list we materialize, matching the saved-filter
|
|
# cap (MAX_SAVED_FILTER_SESSION_IDS_PER_PLAYLIST). The widget itself only ever shows MAX_WIDGET_RESULT_LIMIT.
|
|
MAX_COLLECTION_SESSION_IDS = 1000
|
|
|
|
# Preset relative ranges only — widgets don't accept arbitrary InsightsQL date strings.
|
|
# Note: `M` is minutes, `m` would be months (see insights.utils relative-date parsing).
|
|
WIDGET_DATE_FROM_VALUES_ORDERED: tuple[str, ...] = (
|
|
"-1M",
|
|
"-30M",
|
|
"-1h",
|
|
"-3h",
|
|
"-24h",
|
|
"-7d",
|
|
"-14d",
|
|
"-30d",
|
|
"-90d",
|
|
)
|
|
|
|
WIDGET_DATE_FROM_LABELS: dict[str, str] = {
|
|
"-1M": "Last minute",
|
|
"-30M": "Last 30 minutes",
|
|
"-1h": "Last hour",
|
|
"-3h": "Last 3 hours",
|
|
"-24h": "Last 24 hours",
|
|
"-7d": "Last 7 days",
|
|
"-14d": "Last 14 days",
|
|
"-30d": "Last 30 days",
|
|
"-90d": "Last 90 days",
|
|
}
|