The GitHub Actions job "Build and Run Tests by Bazel" on rocketmq.git/worktree-fix-10559 has failed. Run started by GitHub user Aias00 (triggered by Aias00).
Head commit for run: 4d51ad9997a2168571fab8a294c17dedd816066e / liuhy <[email protected]> [ISSUE #10559] Support wildcard pattern matching for LiteTopic subscriptions Add NATS-style wildcard pattern matching so a wildcard LiteTopic consumer group can subscribe to a subset of lite-topics under its parent topic, using "__" as the segment separator. - LitePatternMatcher (new, common): validate/matches/matchesAny/expand. "*" matches one segment; "**" matches one or more trailing segments. Recursive, no regex; internal pre-split for the expand hot path. - LiteSubscription: add in-memory wildcardPatterns set. - LiteSubscriptionRegistry[Impl]: a wildcard group with non-empty validated patterns enters pattern mode — eagerly expand against collectByParentTopic and register real lmqNames. Empty patterns keep legacy receive-all behavior (synthetic topic@group key) unchanged. getAllSubscriber always merges the synthetic-key clients for any wildcard group so mixed pattern/legacy groups deliver to both; reexpandWildcardPatterns picks up lite-topics created after the initial subscription. - LiteSubscriptionCtlProcessor: route wildcard COMPLETE_ADD through toWildcardPatterns (patterns ride the existing liteTopicSet — no wire change). Non-empty but all-invalid pattern input is rejected instead of silently widening to receive-all. - LiteEventDispatcher.doFullDispatchForWildcardGroup: replace the O(N) forEachLiteTopic scan with O(M) collectByParentTopic; re-expand patterns for new LMQs and clear backlog per pattern-mode client. Full backward compatibility: wildcard groups without patterns behave identically to before. Affected lite tests pass; checkstyle clean. Co-Authored-By: Claude <[email protected]> Report URL: https://github.com/apache/rocketmq/actions/runs/29070279680 With regards, GitHub Actions via GitBox
