yuluo-yx opened a new issue, #4459: URL: https://github.com/apache/rocketmq-dashboard/issues/4459
### Before Creating the Bug Report - [x] I have searched the open 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: master git commit id: 987b748e851d3da94c01e129f0fa61465dcbcf30 deployed as: built from source ### Runtime Environment OS: macOS 26.5.2 MySQL: not required browser: Chrome-compatible browser ### Connected RocketMQ Cluster RocketMQ version: not required access mode: not required deployment: not required ### Build Toolchain JDK: not required Maven: not required Node.js: 23.11.0 locally; frontend package warns that supported engines are 20/22/24+ ### Describe the Bug The frontend delay formatter can render fractional seconds when the input contains millisecond or decimal-second precision. Delay values are shown as operator-facing durations, so fractional carry-over makes compact delay labels noisy and inconsistent with the rest of the UI. ### Steps to Reproduce 1. Call `formatDelay(65.9)` from `web/src/utils/format.ts`. 2. Render the formatted value in a delay or lag label. 3. Observe that seconds are not normalized to whole-second values. ### What Did You Expect to See? Delay labels should use whole seconds, for example `1m 5s`, after truncating sub-second precision. ### What Did You See Instead? The helper may surface fractional-second values in the seconds segment. ### Additional Context This is a small formatting defect found while preparing RocketMQ Studio PRs after the trunk moved to `master`. ### 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]
