Skip to content

Commit 108c1b7

Browse files
Update Rust crate opentelemetry_sdk to v0.32.1 (vortex-data#8178)
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [opentelemetry_sdk](https://redirect.github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-sdk) ([source](https://redirect.github.com/open-telemetry/opentelemetry-rust/tree/HEAD/opentelemetry-sdk)) | workspace.dependencies | patch | `0.32.0` → `0.32.1` | --- > [!WARNING] > Some dependencies could not be looked up. Check the [Dependency Dashboard](..vortex-data/issues/357) for more information. --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-rust (opentelemetry_sdk)</summary> ### [`v0.32.1`](https://redirect.github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-sdk/CHANGELOG.md#0321) Released 2026-May-23 - `BaggagePropagator` now enforces the W3C Baggage maximum header length (8192 bytes) and maximum list-member count (64) when extracting an inbound `baggage` header. Headers exceeding 8192 bytes are dropped at the propagator boundary; headers with more than 64 list members are truncated to the first 64 entries. The change keeps the propagator from parsing attacker-controlled input beyond the W3C limits instead of doing per-entry parse, decode, and allocation work only to discard the excess on `Baggage` insert. See <https://www.w3.org/TR/baggage/#limits>. - Reverted the `SimpleSpanProcessor` telemetry suppression added in 0.32.0 (see [#&vortex-data#8203;3494](https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/3494)), which caused a `RefCell already borrowed` panic when a span was started and dropped inside a `get_active_span` (or `Context::map_current`) closure. Tracked in [#&vortex-data#8203;3510](https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/3510). A proper fix for the underlying `Context::map_current` re-entrancy will be investigated separately, after which the suppression can be safely re-applied. - View-provided metric stream `name` (set via `Stream::builder().with_name(...)`) is no longer validated against the instrument name syntax, per [spec clarification](https://redirect.github.com/open-telemetry/opentelemetry-specification/pull/5094). `unit` and other stream parameters continue to be validated. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - Between 12:00 AM and 03:59 AM, only on Monday (`* 0-3 * * 1`) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/vortex-data/vortex). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMDIuMSIsInVwZGF0ZWRJblZlciI6IjQzLjIwMi4xIiwidGFyZ2V0QnJhbmNoIjoiZGV2ZWxvcCIsImxhYmVscyI6WyJjaGFuZ2Vsb2cvY2hvcmUiXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
1 parent a6b844c commit 108c1b7

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

Cargo.lock

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)