Loyal-Young opened a new issue, #7258: URL: https://github.com/apache/rocketmq-dashboard/issues/7258
## Problem The Mock certificate store includes fixed `status` and `daysRemaining` values that were calculated for its sample data long ago. `listK8sCerts` returns those values unchanged, so a certificate with `notAfter: 2026-06-01` can still appear `valid` with 335 days remaining after it has expired. The certificate page displays and sorts these stale fields directly. The real `K8sCertService.listCerts` recalculates both fields from `notAfter` on each read. Mock mode should reflect that behavior so its status labels and expiry sorting remain truthful over time. ## Reproduction With the clock at 2026-05-20 UTC, list Mock certificate ID 1: it reports `valid` / 335 days rather than `expiring` / 12 days. Advancing to 2026-07-01 should report `expired` / -30 days. A frozen-clock regression fails on the original service. ## Expected Recalculate a listed Mock certificate's remaining whole days and status from its expiration instant on each read, while keeping its stored record and caller-facing SAN array isolated. -- 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]
