zmuxuny opened a new pull request, #6764:
URL: https://github.com/apache/rocketmq-dashboard/pull/6764

   ### Which Issue(s) This PR Fixes
   
   Fixes #6762
   
   ### Brief Description
   
   Require a successful current settings read before editing or saving consumer 
configuration. Pending/failed reads now keep the form and Save disabled, with a 
handler guard as well. A failed read exposes a localized persistent error and 
Retry action. Read start and modal close reset readiness; existing 
request-generation checks prevent stale responses from enabling a newer session.
   
   Preserves optional switch fields and the existing successful-save baseline 
advancement. This differs from #6176/#6182: the reported path never obtains an 
initial baseline.
   
   ### How Did You Test This Change?
   
   - Four new regressions failed on a92c2314; successful-read/edit control 
passed.
   - Full ConsumerPage suite: 60/60 passed; hardened cross-group refresh 
fixture control rerun passed.
   - Changed-file ESLint: zero errors/warnings.
   - TypeScript tsc -b --force passed.
   - Vite production build passed with NODE_OPTIONS=--max-old-space-size=1024; 
license, Prettier and diff checks passed.
   - The initial 1536 MiB heap build was deliberately stopped by the local 2 
GiB free-memory reserve guard during chunk rendering; the single lower-heap 
retry passed without relaxing that guard.
   - Published tree equals the locally tested tree.
   
   ### Checklist
   
   - [x] One coherent change and Conventional Commit
   - [x] Regression tests named ...Test
   - [x] New error text has Chinese and English translations; Retry reuses 
common.retry
   - [x] No new source files
   
   Backend tests were not rerun locally; no backend 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]

Reply via email to