zmuxuny opened a new issue, #7088: URL: https://github.com/apache/rocketmq-dashboard/issues/7088
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version rocketmq-studio at 127c47b06a268cc74224d5f34c56ec7c36ac0d55 ### Runtime Environment Linux, Node.js 24.19.0, frontend Vitest/jsdom tests with real AiPage, synthetic stream and timeline API responses. ### Connected RocketMQ Cluster No RocketMQ cluster or model provider is needed to reproduce this frontend state leak. ### Build Toolchain _No response_ ### Describe the Bug After a measured AI run in one conversation, navigating to another conversation can display the previous conversation's token speed on a historical answer that has no speed measurement. useAgentRun.abort() resets the transcript and stream but retains liveTokensPerSecond and lastRunTokensPerSecond. ### Steps to Reproduce 1. Finish a measured run in conversation 7 (the test measures 1.0 token/s). 2. Navigate through the history to conversation 8. 3. Return a historical assistant answer for conversation 8 without any stored token-speed measurement. 4. Inspect the speed badge on conversation 8. The real routed AiPage regression still finds the 1.0 token/s ai-bubble-speed span. Two hook regressions also fail when switching completed/active runs to a different conversation or the bare /ai route. ### What Did You Expect to See? Speed state and its tracker should reset with conversation ownership. An unmeasured answer in another conversation must not inherit the previous run's speed; the completed-run fallback in the same conversation should still work. ### What Did You See Instead? The historical answer in conversation 8 displays 1.0 token/s from conversation 7. Hook reset assertions also receive 1 instead of null. ### Additional Context Searched all-state issues and PRs for lastRunTokensPerSecond and speed/conversation. #5196 concerns a terminal-update race; #6046 concerns a delayed reporting callback already fixed in this revision. This report is about retained display state across conversation ownership. AI assistance was used for source analysis and regression tests. ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
