tju-yxq opened a new pull request, #2644: URL: https://github.com/apache/rocketmq-dashboard/pull/2644
## What changed Fixes #2643. The trace page already accepts a custom trace topic, but that value was lost in two durable state paths: - rmq_instance_trace stored the message ID and original message topic, not the custom trace topic used by the provider. - The web page kept the current custom topic only in React state, so a refresh or instance remount reverted to the provider default. This change: - stores a trimmed nullable trace_topic for message-ID trace history; - returns and displays the trace topic in the history API/UI, and includes it in history search; - restores the saved topic when a history entry is replayed; - remembers the current custom topic per instance in optional browser storage; - adds an idempotent startup migration for existing rmq_instance_trace tables; - keeps default-topic lookups, pre-existing history rows, provider compatibility, and key-based trace lookups unchanged. ## Verification - Backend focused tests: 32 tests passed. - Backend full test suite: 1,794 tests passed; 0 failures, 0 errors, 0 skipped; Checkstyle violations: 0. - Frontend focused tests: 19 tests passed. - Frontend TypeScript/Vite build: passed. - Frontend lint: 0 errors; 9 existing warnings. - git diff --check: passed. The full frontend run also exposed two pre-existing ConsumerPage.test.tsx timing failures when the entire suite runs in parallel. Running that file alone passes all 21 tests; the three files changed for this PR pass together. -- 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]
