yuluo-yx opened a new pull request, #2851: URL: https://github.com/apache/rocketmq-dashboard/pull/2851
## What is the purpose of the change Consolidate the reviewed frontend interaction and async-lifecycle fixes from #2695, #2706, #2707, #2714, and #2734 into one web correctness pull request, as requested on #2724. The observable failures are: - Reset and query-mode changes leave pagination/truncation state behind and can accept late query results; - opening message content eagerly starts a trace request and repeated trace-tab visits refetch the same trace; - comma-containing message property values are split into malformed records; - two submit events in one render can both call the login API; - About renders stale hard-coded metadata instead of injected build values; - closed/reopened Cluster modals can be overwritten by stale NameServer diff or connection-test responses. The #2691 patch was reimplemented on top of #2839 rather than resolving the old conflict mechanically. Server-backed history snapshot loads now participate in the same request-generation ownership as live queries. ## Brief changelog - clear all message result state and invalidate in-flight work on lifecycle transitions; - load traces only when the Trace tab opens and reuse the same message trace; - preserve commas and additional equals signs in line-based message properties; - synchronously own login submissions; - render actual build commit/time metadata; - apply request generations to Cluster modal requests without removing the newer Broker drift UI. ## Verifying this change - targeted Vitest: 5 files, 45 tests passed; - targeted ESLint passed; - targeted Prettier check passed; - Node 24.18.0 `npm run build` passed (8,025 modules); - `git diff --check` passed; - scope: 11 files, 414 insertions, 50 deletions, 5 commits. Fixes #2691 Fixes #2701 Fixes #2702 Fixes #2711 Fixes #2729 -- 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]
