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
114 lines
2.8 KiB
TypeScript
114 lines
2.8 KiB
TypeScript
import { queryOptions } from "@tanstack/react-query";
|
|
import { api } from "../api";
|
|
|
|
export const dashboardKeys = {
|
|
all: (wsId: string) => ["dashboard", wsId] as const,
|
|
daily: (
|
|
wsId: string,
|
|
days: number,
|
|
projectId: string | null,
|
|
tz: string,
|
|
) => [...dashboardKeys.all(wsId), "daily", days, projectId, tz] as const,
|
|
byAgent: (
|
|
wsId: string,
|
|
days: number,
|
|
projectId: string | null,
|
|
tz: string,
|
|
) => [...dashboardKeys.all(wsId), "by-agent", days, projectId, tz] as const,
|
|
agentRuntime: (
|
|
wsId: string,
|
|
days: number,
|
|
projectId: string | null,
|
|
tz: string,
|
|
) => [...dashboardKeys.all(wsId), "agent-runtime", days, projectId, tz] as const,
|
|
runTimeDaily: (
|
|
wsId: string,
|
|
days: number,
|
|
projectId: string | null,
|
|
tz: string,
|
|
) => [...dashboardKeys.all(wsId), "runtime-daily", days, projectId, tz] as const,
|
|
};
|
|
|
|
// 5-min rollup cadence on the server, 60s background refetch on the client.
|
|
const STALE_TIME = 60 * 1000;
|
|
|
|
// `tz` participates in every dashboard key so a Preferences change
|
|
// repoints the cache. All four series — token rollups and the
|
|
// atq.completed_at-based run-time series — slice their day boundary in
|
|
// the viewer's tz, so the four dashboard tabs always agree.
|
|
export function dashboardUsageDailyOptions(
|
|
wsId: string,
|
|
days: number,
|
|
projectId: string | null,
|
|
tz: string,
|
|
) {
|
|
return queryOptions({
|
|
queryKey: dashboardKeys.daily(wsId, days, projectId, tz),
|
|
queryFn: () =>
|
|
api.getDashboardUsageDaily({
|
|
days,
|
|
project_id: projectId ?? undefined,
|
|
tz,
|
|
}),
|
|
enabled: !!wsId,
|
|
staleTime: STALE_TIME,
|
|
});
|
|
}
|
|
|
|
export function dashboardUsageByAgentOptions(
|
|
wsId: string,
|
|
days: number,
|
|
projectId: string | null,
|
|
tz: string,
|
|
) {
|
|
return queryOptions({
|
|
queryKey: dashboardKeys.byAgent(wsId, days, projectId, tz),
|
|
queryFn: () =>
|
|
api.getDashboardUsageByAgent({
|
|
days,
|
|
project_id: projectId ?? undefined,
|
|
tz,
|
|
}),
|
|
enabled: !!wsId,
|
|
staleTime: STALE_TIME,
|
|
});
|
|
}
|
|
|
|
export function dashboardAgentRunTimeOptions(
|
|
wsId: string,
|
|
days: number,
|
|
projectId: string | null,
|
|
tz: string,
|
|
) {
|
|
return queryOptions({
|
|
queryKey: dashboardKeys.agentRuntime(wsId, days, projectId, tz),
|
|
queryFn: () =>
|
|
api.getDashboardAgentRunTime({
|
|
days,
|
|
project_id: projectId ?? undefined,
|
|
tz,
|
|
}),
|
|
enabled: !!wsId,
|
|
staleTime: STALE_TIME,
|
|
});
|
|
}
|
|
|
|
export function dashboardRunTimeDailyOptions(
|
|
wsId: string,
|
|
days: number,
|
|
projectId: string | null,
|
|
tz: string,
|
|
) {
|
|
return queryOptions({
|
|
queryKey: dashboardKeys.runTimeDaily(wsId, days, projectId, tz),
|
|
queryFn: () =>
|
|
api.getDashboardRunTimeDaily({
|
|
days,
|
|
project_id: projectId ?? undefined,
|
|
tz,
|
|
}),
|
|
enabled: !!wsId,
|
|
staleTime: STALE_TIME,
|
|
});
|
|
}
|