The GitHub Actions job "Run Integration Tests" on rocketmq.git/fix-rocksdb-cq-iteratefrom-min-offset has succeeded. Run started by GitHub user ymwneu (triggered by lizhimins).
Head commit for run: eef8ace8e1179f74c3354982b33ca2c3d369d2ee / maowei.ymw <[email protected]> fix: RocksDBConsumeQueue.iterateFrom should reject offset below min offset startIndex < minOffset was previously accepted as long as it stayed within [0, maxOffset), returning a non-null LargeRocksDBConsumeQueueIterator whose next() can yield a null CqUnit once the underlying data has been purged. Callers like ScheduleMessageService rely on iterateFrom returning null to detect and correct an out-of-range offset (matching ConsumeQueue's getMinLogicOffset() check); without it they NPE dereferencing the null CqUnit instead. Add the same startIndex >= getMinOffsetInQueue() bound used by the file-based ConsumeQueue to both iterateFrom overloads. Report URL: https://github.com/apache/rocketmq/actions/runs/32124493036 With regards, GitHub Actions via GitBox
