[ISSUE #11006]🐛Align OpenTelemetry dependencies and upgrade pending crates - #11007
Merged
Merged
Conversation
Collaborator
|
🔊@mxsm 🚀Thanks for your contribution🎉! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which Issue(s) This PR Fixes(Closes)
Brief Description
Updating tracing-opentelemetry independently to 0.34.0 mixes OpenTelemetry 0.33 types with the 0.32 SDK, causing E0277, E0308, and E0599 errors in tracing layer construction and context propagation. Upgrade the OpenTelemetry API, SDK, exporters, log appender, and semantic conventions together to 0.33.0, and document the version relationship.
Also update rand to 0.10.3 and openraft-macros to 0.10.0-alpha.35, align the fuzz macro pin, and refresh the root, MCP, fuzz, and Web Dashboard backend lockfiles. Add the changelog entry. OpenRaft core and runtime crates remain pinned to alpha.21, explicitly excluding #10192. No Rust API or feature configuration changes are needed.
Consolidates the versions proposed by #10993, #10987, #10986, #10867, #10826, #10824, #10820, #10818, #10817, #10815, #10814, #10813, #10812, #10810, and #10808.
How Did You Test This Change?
Local validation passed on Windows with Rust 1.95.0:
cargo test -p rocketmq-observability --locked, then the same command with each feature set:observability,otlp-metrics,otel-metrics,prometheus,otlp-traces,otlp-logs, andotlp-metrics,otlp-traces,otlp-logs,prometheus. All seven configurations passed; the combined configuration passed 390 tests.cargo test -p rocketmq-controller --locked --no-default-features --features dev-single --test openraft_integration_test: 7 passed.cargo test -p rocketmq-client-rust --locked --lib producer::queue_selector::select_message_queue_by_random: 5 passed.cargo check --locked -p rocketmq-broker -p rocketmq-client-rust -p rocketmq-store -p rocketmq-controller --features rocketmq-broker/otlp-metrics,rocketmq-broker/otlp-traces,rocketmq-broker/otlp-logs,rocketmq-broker/prometheus,rocketmq-controller/metrics-otlp,rocketmq-controller/metrics-prometheus,rocketmq-controller/otlp-traces,rocketmq-controller/otlp-logs: passed after rebuilding a stale local rocketmq-security-api cache artifact.rocketmq-ai/rocketmq-mcp:cargo check --lockedandcargo check --locked --features otlp,streamable-httppassed.rocketmq-dashboard/rocketmq-dashboard-web/backend:cargo check --lockedpassed.fuzz:cargo +nightly-2026-07-05 check --locked --bin controller_snapshot --features controller_snapshotpassed.cargo tree --locked -p rocketmq-observability --features otlp-metrics,otlp-traces,otlp-logs,prometheus -i opentelemetryconfirmed a single API version, 0.33.0.cargo fmt -p rocketmq-controller -p rocketmq-observability -- --checkandgit diff --checkpassed.CI completion is not a merge requirement for this change, as requested by the maintainer.