iloveeyjafjalla opened a new issue, #6674: URL: https://github.com/apache/rocketmq-dashboard/issues/6674
### 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 branch: rocketmq-studio git commit id: e2f815fbf6ee8c9b90e32ce59d6e74f27b0c4ad4 deployed as: built from source (server/ + web/ dev server) against the docker stack in deploy/ ### Runtime Environment OS: Windows 11 24H2 MySQL: 8.x container (host port 13306) browser: Chromium, console served by the Vite dev server ### Connected RocketMQ Cluster RocketMQ version: 5.3.2 access mode: Direct to NameServer/Broker (namesrv 127.0.0.1:9876) deployment: docker (apache/rocketmq:5.3.2, single broker-a), console instance local-broker ### Build Toolchain JDK 21, Maven 3.9, Node.js 20.19.5 ### Describe the Bug The server query history drawer of the message query page prints the recorded query mode as its wire code. The type column shows TOPIC / KEY / MSG_ID, while the mode selector right above the tables names the same three modes 按 Topic 查询 / 按 Message Key / 按 Message ID (Query by Topic / Query by Message Key / Query by Message ID in English). This column is the only place in the console where these values are not named, so an operator reading the history has to decode MSG_ID, and the drawer disagrees with the selector about one and the same value. The API contract is fine - /api/query-history/messages returns queryType as TOPIC | KEY | MSG_ID - only the rendering prints it. ### Steps to Reproduce 1. Open 消息查询 (Instance -> Message) on an instance that has recorded history; any earlier topic / key / message-id query writes a row. 2. Click 服务端历史 to open the drawer. 3. Read the type column of the message-queries table. ### What Did You Expect to See? The recorded mode named the way the search bar names it (按 Message Key / Query by Message Key), with the filter parameters sent to the API unchanged. ### What Did You See Instead? KEY, TOPIC and MSG_ID printed verbatim - in Chinese mode and in English mode alike. ### Additional Context Reproduced on e2f815fbf6ee8c9b90e32ce59d6e74f27b0c4ad4 with four stored rows: - the type column shows KEY, TOPIC, TOPIC, KEY while the selector above reads 按 Topic 查询 / 按 Message Key / 按 Message ID - the dictionary already carries the three names (messagePage.queryMode.topic / .key / .msgid) and the selector renders them - the cell is web/src/components/MessageQueryHistoryDrawer.tsx, messageColumns -> { title: t('common.type'), dataIndex: 'queryType', render: (value) => <Tag>{value}</Tag> } - #3216 localized this drawer's headers in September but left this cell alone ### 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]
