coder999o opened a new pull request, #5359: URL: https://github.com/apache/rocketmq-dashboard/pull/5359
## What is the purpose of the change After a successful Ops configuration load, a later reload can fail while the previous `configurationAvailable` value remains true. The page then leaves NameServer, VIP channel, and TLS write controls enabled against stale configuration. Those controls also remain available while a new reload is pending. ## Brief changelog - Permit Ops writes only when the latest configuration load is ready and supports writes. - Mark each refetch as loading, including a language-triggered reload, until it succeeds or fails. - Cover pending, failed, and recovered reloads for the NameServer controls and VIP/TLS switches. ## Verifying this change - `cd web && npm test -- src/pages/studio/__tests__/Ops.test.tsx` (10 passed). - `cd web && npm test` (1388 passed across 147 test files). - `cd web && npx tsc -b` (passed). - `cd web && npm run lint` (0 errors, 10 existing warnings in unrelated files). - `cd web && npx prettier --check src/pages/studio/Ops.tsx src/pages/studio/__tests__/Ops.test.tsx` (passed). - `git diff --check` (passed). - No live Ops backend reload was run; the page tests use mocked API responses. -- 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]
