coder999o opened a new pull request, #7319: URL: https://github.com/apache/rocketmq-dashboard/pull/7319
## What is the purpose of the change Fixes #7318. Certificate expiry timestamps arrive as offset-less UTC values. The table renders them as UTC but sorts them as browser-local times, which can reverse expiry order across a daylight-saving gap (for example 02:30 and 03:00 on March 8, 2026 in America/New_York). ## Brief changelog - Reuse `parseUtcDateTime` for the expiry comparator, matching the existing formatter and retaining the missing/invalid timestamp fallback. - Add real table ascending/descending regressions in New York, Shanghai, and UTC. No API or storage changes. ## Verifying this change - Before the fix, the new New York regression failed with reversed rows; the Shanghai and UTC controls passed. - `cd web && TZ=America/New_York npm test -- src/pages/cluster/__tests__/K8sCertsPage.test.tsx src/utils/format.test.ts src/services/clusterService.test.ts src/api/cluster.test.ts src/api/clusterContract.test.ts --maxWorkers=1` — 5 files, 71 tests passed. - Certificate page, formatter, and cluster service tests also passed in the default timezone (3 files, 56 tests). - `npx tsc -b --pretty false` passed. Scoped ESLint and Prettier checks passed; `npm run lint` completed with 0 errors and 10 existing warnings outside the changed files. `git diff --check` passed. - These are component/unit checks; no deployed browser or live cluster verification was performed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
