Aias00 opened a new issue, #2620:
URL: https://github.com/apache/rocketmq-dashboard/issues/2620
## Problem
`RocketMQMessageProvider` now limits each topic queue scan to 32 pulls of 32
messages (1,024 messages). Two regression tests still assert the older
1,000-pull / 32,000-message budget, so they fail locally. The backend CI
workflow uses `mvn clean package -DskipTests`, so this failure is not detected
on pull requests.
## Evidence
-
`server/src/main/java/org/apache/rocketmq/studio/provider/apache/RocketMQMessageProvider.java:96`
-
`server/src/test/java/org/apache/rocketmq/studio/provider/apache/RocketMQMessageProviderTest.java:605`
-
`server/src/test/java/org/apache/rocketmq/studio/provider/apache/RocketMQMessageProviderTest.java:626`
- `.github/workflows/ci.yml:35`
JDK 21 reproduction:
```bash
JAVA_HOME=$(/usr/libexec/java_home -v 21) mvn -q \
-Dtest=RocketMQMessageProviderTest#queryByTopicReturnsLatestMessagesWhenWindowExceedsLegacyPullLimit,RocketMQMessageProviderTest#queryByTopicKeepsPullOffsetsInsideTailBudgetWhenWindowIsLargerThanCap
\
test
```
Both tests fail because the actual starts are `38976` and `48976`, while the
test expects the obsolete `8000` and `18000` values.
## Scope
- Update the two regression expectations to prove the current 1,024-message
tail budget.
- Add a backend test job to CI; retain the existing packaging job separately.
- Run the affected tests and the backend test suite in CI.
## Related
The scan-budget change originated in #2544. Open PR #1049 covers frontend
test/lint only.
--
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]
