zmuxuny opened a new pull request, #7380: URL: https://github.com/apache/rocketmq-dashboard/pull/7380
### Which Issue(s) This PR Fixes Fixes #7179. Replaces stale-closed #7180, retaining the original fork branch and authorship. ### Brief Description Add an in-place Retry action when the resource operation timeline read fails. Include a reload generation in the response identity so retry immediately shows loading without losing the current resource, cluster scope, dates, page or page size. The existing request-version guard continues to ignore obsolete responses. Reuses the existing bilingual common.retry label. Net diff against Studio trunk 7abf8ada: 2 files, +154/-2. Open timeline-related requests were checked; no equivalent resource-audit-modal retry fix was found. No backend, API, or dependency changes. ### How Did You Test This Change? Rerun November 4 at f4fbd5a1607b827b38d8520e7244d7b889f00f55: - npm test -- src/pages/ops/__tests__/ResourceOperationTimelineModal.test.tsx: 12 passed, then 12 passed again after the negative control. - The same tests with unchanged trunk production code: 5 failed, 7 passed (missing retry action). - npx tsc -b --force, changed-file ESLint and Prettier: passed. - npm run build: passed, including license check (134 components, 141 license files). Regression coverage includes English/Chinese recovery, filtered page 2, repeated failure then empty success, and a late response after switching resources. Service responses are controlled; AntD modal/date/pagination components are real. No full frontend/backend suite or live cluster was run locally. Hosted CI is separate. AI assistance was used for audit and validation. ### Checklist - [x] One coherent recovery fix with regression tests. - [x] Original authorship and branch retained. - [x] Existing bilingual Retry wording reused. - [x] No new source files, dependencies or public API changes. -- 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]
