Frun1na opened a new issue, #5081: URL: https://github.com/apache/rocketmq-dashboard/issues/5081
### Before creating - [x] I have searched the existing issues and found no duplicate. - [x] I have checked the latest `rocketmq-studio` branch where this problem still exists. ### Bug report **Which page or component** Message detail for cloud (Tencent / Aliyun) instances — `MessageRecordVO.size` and the message page's Size field (`web/src/pages/instance/message.tsx` renders `formatSize(selectedMsg.size)`, so an unknown size shows as `0 B`). **What happened** Cloud providers hardcode the message size to a fabricated `0` when the vendor API does not return one: - Tencent (`TencentInstanceProvider.toRecordVO`, both the `DescribeMessage` and `MessageItem` paths): ```java .size(0) ``` - Aliyun (`AliyunConverters.toMessageRecord`): ```java .size(data.getBodySize() == null ? 0 : data.getBodySize()) ``` The Apache provider reports the real `storeSize`, so the message detail's **Size** field shows `0 B` for every Tencent message (and for Aliyun messages whose `BodySize` is absent) — a fake measurement indistinguishable from a real "this message is empty" reading. **Expected behaviour** Follow the same principle as #4902 (unknown instead of a zero that reads like a measurement): make `MessageRecordVO.size` nullable (or add an unknown sentinel), leave it `null` when the vendor API provides nothing, and render `-` on the web. The same treatment then stays available for the DLQ message path if it inherits the contract. This spans the server VO, both cloud providers and the web type/renderer, and `instance/message.tsx` is currently touched by several open PRs — so I am reporting it for discussion first instead of piling another PR onto that file. I am happy to prepare the fix once the contract direction is agreed. **Environment** - RocketMQ Studio: upstream `rocketmq-studio` tip `a562601d` -- 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]
