zmuxuny opened a new issue, #7211: URL: https://github.com/apache/rocketmq-dashboard/issues/7211
### 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 Source inspected on 2026-10-20 at rocketmq-studio@127c47b06a268cc74224d5f34c56ec7c36ac0d55. Historical real-component reproduction is recorded in #6370 at 779b8c0e7aed2396d3cc72743dcd544ea48e9ae6; no fresh runtime test is claimed here. ### Runtime Environment Studio Topic Send Message frontend. Original reproduction used React/Ant Design with Vitest/jsdom and synthetic service responses. ### Connected RocketMQ Cluster No live cluster. Original tests mocked the send service and inspected its outgoing request; no messages were published. ### Build Toolchain _No response_ ### Describe the Bug Tracking continuation of #6370, automatically closed by github-actions for seven days of inactivity on 2026-10-20. Reopening is unavailable to this account. Existing fix PR #6381 remains open; no new implementation or PR is proposed. Dedicated form fields silently trim leading/trailing whitespace from otherwise nonblank custom-property values. For example, " tenant-blue " is sent as "tenant-blue", changing consumer-visible business data while the input retains the original string. ### Steps to Reproduce 1. Open Topic management and Send for a Topic. 2. Enter a nonempty body and property tenant with value " tenant-blue ". 3. Send and inspect the properties passed to sendTopicMessage. 4. Compare the unchanged input with the trimmed outgoing value. Unicode-padded nonblank values exhibit the same issue. These steps and the real-component regression are documented in #6370; today’s check is source inspection only. ### What Did You Expect to See? Preserve nonblank dedicated-form property values verbatim. Keep property-name normalization, duplicate detection, empty/whitespace-only value behavior, reserved-key handling and batch-text parser semantics unchanged. ### What Did You See Instead? At the inspected revision, buildMessagePropertiesFromRows still assigns const value = rawValue.trim() and stores that value in the properties entries. ### Additional Context Original report: https://github.com/apache/rocketmq-dashboard/issues/6370 Existing fix: https://github.com/apache/rocketmq-dashboard/pull/6381 Current source: https://github.com/apache/rocketmq-dashboard/blob/127c47b06a268cc74224d5f34c56ec7c36ac0d55/web/src/utils/messagePayloadPreview.ts Dated validation remains in #6381: October 15 rebased head 4fb3fad had 91 focused tests and exact-head CI 5/5 passing. This continuation does not claim fresh tests, current CI success, maintainer approval or a merge. Open-issue reference and semantic searches found no equivalent continuation on October 20. AI assistance was used. ### Are You Willing to Submit a Pull Request? - [ ] 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]
