Frun1na opened a new issue, #4939: URL: https://github.com/apache/rocketmq-dashboard/issues/4939
### 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: `1ef5d860` (upstream tip at the time of the report) deployed as: built from source ### Runtime Environment Verified by code tracing and unit tests on `rocketmq-studio` @ `1ef5d860` (vitest for `web/`, JUnit for `server/`), not against a specific browser or deployment. ### Connected RocketMQ Cluster Not cluster-specific: the defect lives in the code path and reproduces on any deployment where the trigger condition below holds. ### Describe the Bug Opening the cluster config modal rounds the persisted `maxMessageSize` down/up to whole MiB for display, and submitting multiplies the rounded number back. A no-op save therefore mutates the broker's maxMessageSize whenever the persisted value is not MiB-aligned. ### Steps to Reproduce 1. Persist a broker `maxMessageSize` that is not a whole MiB (e.g. 4194304 + 524288). 2. Open the config modal, change nothing, click OK. 3. The broker now stores the MiB-rounded value instead of the original bytes. ### What Did You Expect to See? A no-op save preserves the persisted configuration byte for byte. ### What Did You See Instead? The value is silently rounded. -- 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]
