The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/tencent-message-query-offset has failed. Run started by GitHub user lizhimins (triggered by lizhimins).
Head commit for run: 76ca55bf7094ca1b80a3f7b69ea8a8b8aab8a1d0 / Apulupie <[email protected]> fix(tencent): page the message query by consumed rows, not collected records `queryMessagesDetailed` derived the next page offset from the records it had collected (`request.setOffset((long) result.size())`) instead of the rows the API had already returned. The SDK maps a JSON null array element to a null element and the loop skips it, so every skipped entry made the next offset one row too small: the API re-returned the tail of the page, the result contained duplicate msgIds, and `isLastPage(..., result.size())` made the completion check drift by the same amount. The Aliyun sibling counts raw provider rows in its paging bookkeeping, and this file already guards null array elements in three places. A `fetchedRows` counter now grows by `returned` on every page and feeds both the next offset and the last-page check; `result.size()` keeps serving only the result budget. The duplicated short-page comment above `isLastPage` is removed while editing those lines. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38721842940 With regards, GitHub Actions via GitBox
