mirror of
https://github.com/multica-ai/multica.git
synced 2026-06-17 03:38:32 +02:00
614dfae884
* docs(timezone): add scheduling/viewing timezone architecture RFC * feat(db): replace daily rollups with task_usage_hourly, add user.timezone Migrations 100-104: add "user".timezone (Viewing tz), build the UTC hourly task_usage_hourly rollup with its pipeline, drop the legacy task_usage_daily / task_usage_dashboard_daily pipelines, and drop the agent_runtime.timezone column. Report queries now slice day boundaries at read time by the caller-supplied @tz instead of materialising in a fixed tz. Regenerate sqlc. * feat(server): add task_usage_hourly backfill command Replace the two legacy backfill commands (daily / dashboard_daily) with a single backfill_task_usage_hourly that loads historical task_usage into the new UTC hourly rollup, sliced per workspace. * refactor(server): resolve viewing timezone in report handlers Report handlers resolve the Viewing tz per request (?tz query param, then user.timezone, then UTC) and pass it to the hourly-rollup queries. Drop the UseDailyRollup feature flags and the old raw-scan/daily-rollup dual paths, remove the /api/usage endpoints, and stop the daemon from reporting and the runtime handler from accepting host timezone. * refactor(core): switch report queries to viewing timezone API client and dashboard/runtime queries send ?tz with each report request, the user schema/types carry the new timezone field, and the runtime timezone field/mutation is removed. * feat(views): add viewing timezone preference and UI Add the useViewingTimezone hook and a Timezone setting in Preferences; report charts and the dashboard week boundary follow the viewer tz. Remove the runtime detail timezone editor and its locale strings. * fix(test): update fixtures and stabilize tests for timezone refactor The timezone architecture refactor changed several types without updating dependent test code: - RuntimeDevice no longer has a timezone field — drop it from the create-agent-dialog runtime fixture. - User now requires a timezone field — add it to the apps/web mockUser fixture. - The PreferencesTab timezone tests asserted on the async save handler (PATCH then store update) with a bare expect, racing the mutation's settle callback, and timed out querying the Select's ~600-option IANA list on a loaded CI runner. Wrap the assertions in waitFor and extend the timeout for those three tests. * docs(timezone): document self-host migration order and trigger invariant Add a SELF-HOST UPGRADE ORDER runbook to the backfill command's package comment: applying migrations 100-104 in a single migrate-up drops the legacy daily rollups before the hourly backfill runs, leaving dashboards empty until cron catches up. Add an INVARIANT comment on trg_atq_dirty_hourly noting that agent_id must be added to the trigger's OF list if it ever becomes mutable, otherwise dirty buckets for the old agent_id are silently missed. * style(runtimes): drop trailing blank line in runtime-detail
32 lines
1.4 KiB
SQL
32 lines
1.4 KiB
SQL
-- Unschedule the cron job first — the operator playbook in the up
|
|
-- migration registers it, so a rollback must clear it before the
|
|
-- function it calls is dropped, or the still-registered job ticks into
|
|
-- a `function does not exist` error. Guarded so rollback still succeeds
|
|
-- where pg_cron is absent or the job was never registered (same pattern
|
|
-- as migration 103).
|
|
DO $$
|
|
BEGIN
|
|
IF EXISTS (SELECT 1 FROM pg_extension WHERE extname = 'pg_cron') THEN
|
|
PERFORM cron.unschedule('rollup_task_usage_hourly')
|
|
FROM cron.job WHERE jobname = 'rollup_task_usage_hourly';
|
|
END IF;
|
|
END
|
|
$$;
|
|
|
|
DROP TRIGGER IF EXISTS trg_tu_dirty_hourly ON task_usage;
|
|
DROP TRIGGER IF EXISTS trg_issue_project_dirty_hourly ON issue;
|
|
DROP TRIGGER IF EXISTS trg_issue_delete_dirty_hourly ON issue;
|
|
DROP TRIGGER IF EXISTS trg_atq_dirty_hourly ON agent_task_queue;
|
|
|
|
DROP FUNCTION IF EXISTS task_usage_hourly_rollup_lag_seconds();
|
|
DROP FUNCTION IF EXISTS rollup_task_usage_hourly();
|
|
DROP FUNCTION IF EXISTS prune_task_usage_hourly_dirty(INTERVAL);
|
|
DROP FUNCTION IF EXISTS rollup_task_usage_hourly_window(TIMESTAMPTZ, TIMESTAMPTZ);
|
|
|
|
DROP FUNCTION IF EXISTS enqueue_task_usage_hourly_dirty_for_tu();
|
|
DROP FUNCTION IF EXISTS enqueue_task_usage_hourly_dirty_for_issue_project();
|
|
DROP FUNCTION IF EXISTS enqueue_task_usage_hourly_dirty_for_issue_delete();
|
|
DROP FUNCTION IF EXISTS enqueue_task_usage_hourly_dirty_for_atq();
|
|
|
|
DROP FUNCTION IF EXISTS task_usage_hour_bucket(TIMESTAMPTZ);
|