mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-06 14:00:09 +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
77 lines
2.5 KiB
SQL
77 lines
2.5 KiB
SQL
-- name: GetUser :one
|
|
SELECT * FROM "user"
|
|
WHERE id = $1;
|
|
|
|
-- name: GetUserByEmail :one
|
|
SELECT * FROM "user"
|
|
WHERE email = $1;
|
|
|
|
-- name: CreateUser :one
|
|
INSERT INTO "user" (name, email, avatar_url)
|
|
VALUES ($1, $2, $3)
|
|
RETURNING *;
|
|
|
|
-- name: UpdateUser :one
|
|
-- Patches the user-controlled profile fields. Each parameter follows
|
|
-- COALESCE-on-NULL semantics so the handler can omit any field it
|
|
-- doesn't intend to write.
|
|
--
|
|
-- `timezone` (Viewing-tz preference) participates in
|
|
-- the same shape but uses sqlc.narg + a sentinel-string convention:
|
|
-- the handler passes the empty string "" to mean "clear back to NULL"
|
|
-- (browser-detected fallback), an IANA name like "Asia/Shanghai" to
|
|
-- pin a value, and `sqlc.narg('timezone') IS NULL` (no value at all)
|
|
-- to leave the existing column untouched. Folding it into UpdateUser
|
|
-- rather than carrying a dedicated UpdateUserTimezone keeps the
|
|
-- profile-patch shape uniform between Preferences fields.
|
|
UPDATE "user" SET
|
|
name = COALESCE($2, name),
|
|
avatar_url = COALESCE($3, avatar_url),
|
|
language = COALESCE($4, language),
|
|
profile_description = COALESCE(sqlc.narg('profile_description'), profile_description),
|
|
timezone = CASE
|
|
WHEN sqlc.narg('timezone')::text IS NULL THEN timezone
|
|
WHEN sqlc.narg('timezone')::text = '' THEN NULL
|
|
ELSE sqlc.narg('timezone')::text
|
|
END,
|
|
updated_at = now()
|
|
WHERE id = $1
|
|
RETURNING *;
|
|
|
|
-- name: MarkUserOnboarded :one
|
|
UPDATE "user" SET
|
|
onboarded_at = COALESCE(onboarded_at, now()),
|
|
updated_at = now()
|
|
WHERE id = $1
|
|
RETURNING *;
|
|
|
|
-- name: PatchUserOnboarding :one
|
|
UPDATE "user" SET
|
|
onboarding_questionnaire = COALESCE(sqlc.narg('questionnaire'), onboarding_questionnaire),
|
|
updated_at = now()
|
|
WHERE id = sqlc.arg('id')
|
|
RETURNING *;
|
|
|
|
-- name: JoinCloudWaitlist :one
|
|
-- Records interest in cloud runtimes. Does NOT mark onboarding
|
|
-- complete — the user still has to pick a real path (CLI / Skip)
|
|
-- in Step 3. Repeating the call overwrites email + reason.
|
|
UPDATE "user" SET
|
|
cloud_waitlist_email = $2,
|
|
cloud_waitlist_reason = $3,
|
|
updated_at = now()
|
|
WHERE id = $1
|
|
RETURNING *;
|
|
|
|
-- name: SetStarterContentState :one
|
|
-- Atomically transition starter_content_state. The handler is
|
|
-- responsible for checking the current value first (to decide between
|
|
-- "transition NULL -> imported and run the seeding" vs "already
|
|
-- decided, short-circuit"). Using COALESCE here would swallow the
|
|
-- transition, so this is a straight assignment.
|
|
UPDATE "user" SET
|
|
starter_content_state = $2,
|
|
updated_at = now()
|
|
WHERE id = $1
|
|
RETURNING *;
|