supabase / supabase / 42049118382

87%

push

github

fix(studio): keep service health windows within DST limits FE-4928 (#53027)

## Problem

The home dashboard's 7-day charts can fail after daylight saving time
ends. Subtracting seven local calendar days produces a 169-hour request,
exceeding the service-health endpoint's 168-hour limit. The same
calculation also changes the 24-hour window across DST transitions.

## Fix

Calculate the shared service-health windows using 24 and 168 elapsed
hours. Add regression coverage for both daylight saving transitions in
America/New_York.

Fixes
[FE-4928](https://linear.app/supabase/issue/FE-4928/re-dashboard-is-not-showing-correct-data).

## How to test

- Run `pnpm --dir apps/studio exec vitest run --retry=0
components/interfaces/Observability/useServiceHealthMetrics.utils.test.ts`.
- In a browser using America/New_York around the November 1 DST
transition, open a project's home dashboard and select the 7-day view.
- Expected result: the service-health request spans exactly 168 hours
and the charts load. The 24-hour view spans exactly 24 hours across
either DST transition.

Local verification: Studio typecheck, focused ESLint, Prettier, and 41
affected tests pass. All four DST regressions fail against the original
helper and pass with the fix; shuffled tests also pass with seed 4928
and TZ=UTC.

2042 of 2411 branches covered (84.7%)

Branch coverage included in aggregate %.

2838 of 3198 relevant lines covered (88.74%)

201.27 hits per line