ai-yang commented on PR #10751:
URL: https://github.com/apache/rocketmq/pull/10751#issuecomment-5447350018
Status refresh (2026-08-28):
- Rebased the PR onto the latest upstream `develop` (`e348efa66`). New head:
`7cb64c7a8`.
- Rechecked the current upstream implementation: no equivalent fix has
landed, and timeout cleanup can still remove a lock after a concurrent
reacquisition without this patch, breaking per-key mutual exclusion.
- Re-ran the targeted broker reactor on the rebased head:
`mvn -Dmaven.repo.local=/tmp/codex-maven-repository -pl broker -am
-DskipITs -Dtest=org.apache.rocketmq.broker.pop.PopConsumerLockServiceTest
-Dsurefire.failIfNoSpecifiedTests=false test`
Result: **BUILD SUCCESS**; 2 tests run, 0 failures, 0 errors. Checkstyle
and SpotBugs also passed in the reactor.
No additional implementation changes were needed after the rebase. The issue
remains actionable and this PR is not superseded by current `develop`.
--
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]
