Files
multica/packages/core/runtimes/queries.ts
YYClaw 614dfae884 MUL-2488 feat(timezone): Scheduling / Viewing two-layer timezone architecture (#2968)
* 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
2026-05-21 15:33:47 +08:00

79 lines
2.5 KiB
TypeScript

import { queryOptions } from "@tanstack/react-query";
import { api } from "../api";
export const runtimeKeys = {
all: (wsId: string) => ["runtimes", wsId] as const,
list: (wsId: string) => [...runtimeKeys.all(wsId), "list"] as const,
listMine: (wsId: string) => [...runtimeKeys.all(wsId), "list", "mine"] as const,
usage: (rid: string, days: number, tz: string) =>
["runtimes", "usage", rid, days, tz] as const,
usageByAgent: (rid: string, days: number, tz: string) =>
["runtimes", "usage", "by-agent", rid, days, tz] as const,
// by-hour now follows the viewer's tz, like the other reports.
usageByHour: (rid: string, days: number, tz: string) =>
["runtimes", "usage", "by-hour", rid, days, tz] as const,
latestVersion: () => ["runtimes", "latestVersion"] as const,
};
// `tz` is the viewer's IANA name — all reports follow the viewer's tz.
export function runtimeUsageOptions(
runtimeId: string,
days: number,
tz: string,
) {
return queryOptions({
queryKey: runtimeKeys.usage(runtimeId, days, tz),
queryFn: () => api.getRuntimeUsage(runtimeId, { days, tz }),
staleTime: 60 * 1000,
});
}
export function runtimeUsageByAgentOptions(
runtimeId: string,
days: number,
tz: string,
) {
return queryOptions({
queryKey: runtimeKeys.usageByAgent(runtimeId, days, tz),
queryFn: () => api.getRuntimeUsageByAgent(runtimeId, { days, tz }),
staleTime: 60 * 1000,
});
}
export function runtimeUsageByHourOptions(runtimeId: string, days: number, tz: string) {
return queryOptions({
queryKey: runtimeKeys.usageByHour(runtimeId, days, tz),
queryFn: () => api.getRuntimeUsageByHour(runtimeId, { days, tz }),
staleTime: 60 * 1000,
});
}
export function runtimeListOptions(wsId: string, owner?: "me") {
return queryOptions({
queryKey: owner === "me" ? runtimeKeys.listMine(wsId) : runtimeKeys.list(wsId),
queryFn: () => api.listRuntimes({ workspace_id: wsId, owner }),
});
}
const GITHUB_RELEASES_URL =
"https://api.github.com/repos/multica-ai/multica/releases/latest";
export function latestCliVersionOptions() {
return queryOptions({
queryKey: runtimeKeys.latestVersion(),
queryFn: async (): Promise<string | null> => {
try {
const resp = await fetch(GITHUB_RELEASES_URL, {
headers: { Accept: "application/vnd.github+json" },
});
if (!resp.ok) return null;
const data = await resp.json();
return (data.tag_name as string) ?? null;
} catch {
return null;
}
},
staleTime: 10 * 60 * 1000, // 10 minutes
});
}