tju-yxq commented on PR #2644: URL: https://github.com/apache/rocketmq-dashboard/pull/2644#issuecomment-5528697422
Rebased onto the current `rocketmq-studio` and re-applied the custom trace-topic persistence on top of #2839's result-snapshot model and #2851's message-page lifecycle changes in `730045a1`. The conflict resolution preserves the mainline snapshot/replay and request-generation behavior. The custom topic is now integrated into the current schema migration, nullable history model/API, history replay, per-instance preference, and trace cache key without replacing those mainline safeguards. Verification after the rebase: - backend focused tests: 28 passed; - full server suite: 1,966 passed, 0 failures/errors/skips; - frontend focused changed-file tests: 23 passed; - related message-page tests: 9 passed standalone; - TypeScript/Vite production build: passed; - ESLint: 0 errors (11 existing warnings); - `git diff --check`: clean. I also attempted the full parallel frontend suite: 809/836 passed, while 27 tests across 11 files hit the common 20-second timeout under parallel load, including unrelated ACL, consumer, alert, audit, cluster, and settings tests. The changed and related message/query-history tests pass in focused runs. The PR is now mergeable/CLEAN, and GitHub has not attached status checks to the new head yet. -- 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]
