RockteMQ-AI commented on issue #2620: URL: https://github.com/apache/rocketmq-dashboard/issues/2620#issuecomment-5420845391
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported regression is verified against the current codebase: - `RocketMQMessageProvider.java` defines `MAX_PULLS_PER_QUEUE = 32` and `TOPIC_PULL_BATCH_SIZE = 32`, giving a per-queue budget of **1,024 messages** (`MAX_TOPIC_SCAN_MESSAGES_PER_QUEUE`). - The two tests (`queryByTopicReturnsLatestMessagesWhenWindowExceedsLegacyPullLimit`, `queryByTopicKeepsPullOffsetsInsideTailBudgetWhenWindowIsLargerThanCap`) still assert offsets derived from the legacy 1,000-pull / 32,000-message budget. - `.github/workflows/ci.yml` runs `mvn clean package -DskipTests`, so these failures are not caught in CI. **Root Cause:** Test expectations were not updated when the scan-budget change landed (#2544). **Impact:** Regression coverage for topic tail-query is effectively broken; developers cannot rely on these tests locally. **Severity:** medium — tests fail locally but CI does not gate on them. Proposed scope is reasonable: 1. Update the two test assertions to match the 1,024-message tail budget. 2. Add a backend test job to CI (separate from the existing packaging job). An automated fix proposal can be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by RockteMQ-AI* -- 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]
