tju-yxq opened a new pull request, #2032:
URL: https://github.com/apache/rocketmq-dashboard/pull/2032

   ## What is the purpose of the change
   
   Follow-up regression coverage for earlier provider fixes that are already 
present in current `rocketmq-studio`.
   
   This PR covers repository-verifiable behavior related to #1353, #1394, and 
#1401. The related issues originally contained live-environment style 
reproduction language; this follow-up is intentionally limited to code 
inspection and focused unit tests. It was not live-tested against a RocketMQ 
broker or cloud/ONS environment.
   
   ## Brief changelog
   
   - Added topic message-query coverage showing `OFFSET_ILLEGAL` retries from 
the broker-provided corrected offset and still returns later messages.
   - Added DLQ resend coverage showing `OFFSET_ILLEGAL` retries from the 
corrected offset and still resends later dead-letter messages.
   - Added direct coverage for the shared `SystemGroupFilter` prefixes used by 
client, metadata, and dashboard providers.
   - Re-ran existing dashboard count tests for per-cluster topic/group counting.
   
   ## Verification
   
   ```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`.
   
   ## Notes
   
   - No live retention-cleanup, broker restart, ONS, or UI reproduction was 
performed.
   - Full project verification was not 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]

Reply via email to