tju-yxq commented on issue #1353: URL: https://github.com/apache/rocketmq-dashboard/issues/1353#issuecomment-5269980474
Follow-up audit note: This is fixed in current `rocketmq-studio`. The topic message query and DLQ resend scan loops now handle `OFFSET_ILLEGAL` by advancing to the broker-provided `nextBeginOffset` and retrying from the corrected offset, with a consecutive-illegal guard. Follow-up PR #2032 adds focused regression coverage for both paths. Verification run: ```bash cd server mvn -DskipTests=false "-Dtest=RocketMQMessageProviderTest#queryByTopicRetriesFromCorrectedOffsetAfterOffsetIllegal,RocketMQDLQProviderTest#resendMessagesRetriesFromCorrectedOffsetAfterOffsetIllegal,SystemGroupFilterTest,RocketMQDashboardProviderTest#dashboardShouldCountTopicsFromBrokerConfigWithoutPerTopicRouteRequests+dashboardShouldDeduplicateGroupsReportedByMultipleClusterBrokers" test ``` Result: `BUILD SUCCESS`; `Tests run: 5, Failures: 0, Errors: 0, Skipped: 0`. I updated the issue description to remove unverified live retention-cleanup/broker-restart reproduction claims. The current evidence is code inspection plus mocked unit tests; no live broker scenario was run. -- 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]
