zmuxuny opened a new pull request, #6652:
URL: https://github.com/apache/rocketmq-dashboard/pull/6652

   ### Which Issue(s) This PR Fixes
   
   Fixes #6627.
   
   ### Brief Description
   
   Report zero delay when complete offset evidence proves that a consumer is 
caught up and the consumed timestamp is available. Apply the same rule to 
inventory and group-detail paths. Keep positive/unknown-lag behavior and 
unavailable timestamps unchanged, including #6187's unknown-data semantics.
   
   ### Verification
   
   Base: rocketmq-studio@779b8c0e7aed2396d3cc72743dcd544ea48e9ae6.
   
   The following validation was completed on October 13, 2026 against the 
prepared source. The fork head and tree were rechecked on October 14; these 
tests are not claimed as a fresh rerun.
   
   188 focused backend tests passed. The regression exercises the real 
provider, native collector and alert evaluator, including caught-up idle groups 
and positive/unknown-lag and missing-timestamp controls.
   
   A separate combined verification snapshot containing the five backend fixes 
in this batch and existing #5192 passed 559 focused tests. Packaging, 
Checkstyle and the normal binary-license gate passed (278 components). The 
combined full backend run was not green: 3,573 executed, 3,537 passed, 18 
failures and 18 errors. All 36 failing/error cases matched a clean base under 
the same URL-fixture environment settings. These combined-snapshot results are 
not presented as a standalone full-suite pass for this PR. Java 21, Maven 
3.9.11 and an explicit Mockito Java agent were used; no license gate was 
bypassed.
   
   Independent source/test review completed. AI assistance was used for 
implementation and regression authoring. Controlled fixtures were used; no live 
production incident, deployment or broker mutation is claimed. Upstream CI for 
this new PR remains to be verified.
   


-- 
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