lizhimins opened a new pull request, #10404: URL: https://github.com/apache/rocketmq/pull/10404
## Summary - Replace outdated/incorrect Bazel WORKSPACE artifacts to match Maven pom.xml (source of truth) - Fix the root cause of flaky Bazel CI test failures (RocksDB JNI SIGSEGV caused by using wrong artifact `rocketmq-rocksdb:1.0.6` instead of `org.rocksdb:rocksdbjni:8.4.4`) - Bump 16 dependency versions, fix 3 artifact coordinate mismatches, add 3 missing deps ## Key Changes | Category | Change | |----------|--------| | **Critical fix** | `org.apache.rocketmq:rocketmq-rocksdb:1.0.6` → `org.rocksdb:rocksdbjni:8.4.4` | | **Artifact rename** | `org.lz4:lz4-java:1.8.0` → `at.yawk.lz4:lz4-java:1.10.3` | | **Artifact rename** | `org.bouncycastle:bcpkix-jdk15on:1.69` → `bcpkix-jdk18on:1.83` | | **Version bumps** | netty-all, guava, grpc-*, commons-lang3, commons-io, gson, okio, etc. | | **Missing deps** | Added `slf4j-api:2.0.3`, `javassist:3.20.0-GA`, `grpc-protobuf:1.53.0` | | **Cleanup** | Removed duplicate `fastjson2` entry | | **Build fix** | Added `--nojava_header_compilation` (netty-all 4.1.130+ is POM-only) | ## Motivation The Bazel CI (`bazel-compile`) has been failing with JVM SIGSEGV crashes on RocksDB-related tests. Root cause: WORKSPACE declared `rocketmq-rocksdb:1.0.6` (an obsolete shim package) while Maven uses the official `org.rocksdb:rocksdbjni:8.4.4`. The native library version mismatch causes segfaults. Additionally, 15+ other dependencies had drifted between Maven and Bazel, creating a maintenance burden and potential for subtle runtime differences. ## Test plan - [x] `bazel build //...` passes locally (583 targets) - [x] `bazel test //...` — 487/552 pass, 65 failures are pre-existing sandbox filesystem issues unrelated to this change - [x] All Maven CI checks (ubuntu/macOS/windows) unaffected (no pom.xml changes) 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
