zmuxuny opened a new issue, #6752: URL: https://github.com/apache/rocketmq-dashboard/issues/6752
### 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 a92c23144408cdf5729707050e9ecd9b75f1bad0 ### Runtime Environment Linux, Node24.19.0, Vitest/jsdom. Real ConsumerPage and Ant Design with controlled service data. ### Connected RocketMQ Cluster Synthetic queue response; no live broker required. Topic and broker identifiers contain ordinary hyphens. ### Build Toolchain _No response_ ### Describe the Bug The progress table concatenates topic, broker and queue id with hyphens for its React row key. Different valid tuples can collide. After filtering, React reconciliation retains an excluded queue, showing misleading consumption progress. ### Steps to Reproduce 1. Return three queues (topic,broker,id,lag): (orders-west,a,0,10), (orders,west-a,0,20), (payments,b,0,30). 2. Open consumer group details, Consumption progress. 3. Select Topic=payments. ### What Did You Expect to See? Exactly the payments queue remains rendered, matching the filtered data. ### What Did You See Instead? Two rows remain rendered; an excluded orders-west row survives. React also reports duplicate key orders-west-a-0. A real-component regression fails with expected row count1 but actual2, not merely a console warning. ### Additional Context Source consumer.tsx around696–712 filters correctly; rowKey around2186 collapses distinct tuples. Use a stable collision-free tuple identity without changing filters or real identifiers. All-state issues/PRs searched for queue rowKey/progress/delimiter/collision/identity/hyphen. #2074 concerns subscription rows; #1339 global group/instance rows; #5101 tool output omission. React key contract: https://react.dev/learn/rendering-lists#rules-of-keys . Reset preview has similar syntax but is single-topic, so this report only claims the demonstrated consumption-progress defect. ### 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]
