zmuxuny opened a new issue, #4528: URL: https://github.com/apache/rocketmq-dashboard/issues/4528
### Before Creating the Bug Report - [x] I searched open/closed issues and PRs for Tencent `DescribeInstanceList`, incomplete catalog pages, null `Data`, and `TotalCount` handling. - [x] I reproduced the behavior on current `master` (`d50ffec`). ### Problem `TencentCatalogService.listCloudInstances` stops pagination whenever the current `DescribeInstanceList` response has `Data == null` or an empty array. It does this before consulting `TotalCount`. Tencent's RocketMQ 5.x API defines `TotalCount` as the total query count and `Data` as the instance list. If a response says `TotalCount > current offset` while the current page has no data, the provider response is incomplete/contradictory: Studio currently converts that into a successful truncated catalog. ### Impact Cloud-instance discovery/onboarding can show an empty or partial Tencent instance inventory as complete. Operators may conclude an instance does not exist or is not accessible even though the provider reports more matching instances. ### Expected behavior - If `TotalCount` proves rows remain but the current page has no `Data`, fail closed with a 502-style error. - Preserve a genuine empty catalog when `TotalCount` is zero/absent and no rows are returned. - Preserve existing pagination, search filtering, and count normalization behavior. ### Red reproduction On unmodified `master`, add a `DescribeInstanceListResponse` with `TotalCount=1` and `Data=null`, then require `listCloudInstances` to return 502. `TencentCatalogServiceTest`: **9 tests, exactly 1 failure** (`Expecting code to raise a throwable`) because current code returns an empty list. ### Relation to existing work #4513/#4514 cover the same completeness principle for Tencent message-query pages; this issue is the separate cloud-catalog/onboarding path. AI-assisted source audit and regression authoring; Tencent's current `DescribeInstanceList` API documentation and the pinned Java SDK model were checked before filing. -- 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]
