unbridled-41 opened a new issue, #5951:
URL: https://github.com/apache/rocketmq-dashboard/issues/5951
### Studio Version
branch: `rocketmq-studio` @ `7e7aa344` (the revision verified; the branch is
based on it)
deployed as: not required to reproduce
### Runtime Environment
Reproduced with the frontend tests (`cd web && npx vitest run
src/pages/settings/__tests__/CloudCredentialTab.test.tsx`).
### Connected RocketMQ Cluster
Not involved.
### Describe the Bug
The Cloud Credentials table renders the field verbatim:
```tsx
{ title: t('settings.createdAt'), dataIndex: 'gmtCreate', key: 'gmtCreate' },
```
so the cell shows the API's zoneless wire value - `2026-08-18T10:00:00`,
with the ISO `T` separator and no zone handling - while every sibling inventory
formats the same `BaseEntity` field (Studio users via `formatUtcDateTime`, the
instance list via `formatDateTime`, the ACL tables via `formatDate`).
`CloudCredentialService` stamps it with the server clock like the rest of the
metadata rows, which is what `formatDateTime` renders.
### Steps to Reproduce
1. Open Settings → Cloud Credentials.
2. The 创建时间 column reads `2026-08-18T10:00:00` (or the server's raw stamp
for real rows).
### What Did You Expect to See?
The formatted timestamp every other inventory column shows.
### What Did You See Instead?
The raw wire value.
### Evidence
- `web/src/pages/settings/CloudCredentialTab.tsx` (the column),
`server/.../provider/credential/CloudCredentialService.java`,
`web/src/utils/format.ts`.
- `cd web && npx vitest run
src/pages/settings/__tests__/CloudCredentialTab.test.tsx -t 'created
timestamp'` - fails before the fix (`expected document not to contain element,
found <td`).
### Impact
The credentials inventory shows an unformatted, zone-less timestamp where
every sibling table shows a readable one.
### Acceptance Criteria
- The column renders through the shared formatter (with `-` for an absent
value), with a regression test.
**Corresponding PR:** #ISSUEPR#
--
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]
