123123213weqw opened a new pull request, #7324:
URL: https://github.com/apache/rocketmq-dashboard/pull/7324

   Fixes #7318 and fixes #7250.
   
   **#7318 — certificate expiry sorting:** `certs.tsx` sorted `notAfter` values 
(offset-less UTC strings) with `Date.parse`, which reads them as the viewer's 
local wall clock; in `America/New_York` the spring-forward gap normalizes a 
nonexistent 02:30 local to 03:30, ranking the earlier 02:30 UTC certificate 
after the later 03:00 UTC one across the viewer-day boundary. The UTC 
normalization previously inlined in `formatUtcDateTime` is now extracted as 
`parseUtcDateTime` in `utils/format` and reused by the sorter, so the order 
follows the absolute instant; the missing/invalid fallback is unchanged.
   
   **#7250 — consumer progress interleaving:** the frontend was already correct 
(rows sort topic → broker → queueId with composite rowKeys); the actual defect 
is in the backend `RocketMQMetadataProvider` progress sort, which ordered by 
broker (ignore-case) then queue ID only, letting topics with equal queue IDs 
interleave. The sort now tie-breaks case-sensitively by topic and then by queue 
ID, exactly as the issue specifies.
   
   Red-first on both: the DST sort test flips on base with 
`process.env.TZ='America/New_York'`; the backend test fails with the issue's 
exact interleaving `[(TopicB,0), (TopicA,0), (TopicA,1)]`. Web suites 45/45, 
`RocketMQMetadataProviderTest` 55/55.
   


-- 
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]

Reply via email to