Update `opentelemetry` Rust crates to 0.32.0 by hash-worker[bot] · Pull Request #8013 · hashintel/hash

hash-worker · 2025-11-05T00:34:20Z

This PR contains the following updates:

Package	Type	Update	Change	Pending
opentelemetry (source)	workspace.dependencies	minor	`0.30.0` → `0.32.0`
opentelemetry-appender-tracing (source)	workspace.dependencies	minor	`0.30.1` → `0.32.0`
opentelemetry-otlp (source)	workspace.dependencies	minor	`0.30.0` → `0.32.0`
opentelemetry-semantic-conventions (source)	workspace.dependencies	minor	`0.30.0` → `0.32.0`
opentelemetry_sdk (source)	workspace.dependencies	minor	`0.30.0` → `0.32.0`
tracing-opentelemetry	workspace.dependencies	minor	`0.31.0` → `0.32.0`	`0.33.0`

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

`v0.32.0`

Compare Source

Released 2026-May-08

Added BoundCounter<T> and BoundHistogram<T> types that cache resolved
aggregator references for a fixed attribute set. Created via Counter::bind()
and Histogram::bind(), bound instruments bypass per-call attribute lookup,
providing significant performance improvements for hot paths where the same
attributes are used repeatedly. Both types implement Clone so a single bound
state can be shared across threads or modules without re-binding. Also adds
the SyncInstrument::bind() trait method and BoundSyncInstrument<T> trait
for SDK implementors; the trait method has a no-op default so custom
SyncInstrument impls degrade gracefully without panicking. Gated behind the
experimental_metrics_bound_instruments feature flag.
Add reserve method to opentelemetry::propagation::Injector to hint at the number of elements that will be added to avoid multiple resize operations of the underlying data structure. Has an empty default implementation.
Breaking Removed the following public fields and methods from the SpanBuilder #3227:
- trace_id, span_id, end_time, status, sampling_result
- with_trace_id, with_span_id, with_end_time, with_status, with_sampling_result
Added #[must_use] attribute to opentelemetry::metrics::AsyncInstrumentBuilder to add compile time warning when .build() is not called on observable instrument builders, preventing silent failures where callbacks are never registered and metrics are never reported.
Breaking Moved the following SDK sampling types from opentelemetry::trace to opentelemetry_sdk::trace #3277:
- SamplingDecision, SamplingResult
- These types are SDK implementation details and should be imported from opentelemetry_sdk::trace instead.
"spec_unstable_logs_enabled" feature flag is removed. The capability (and the
backing specification) is now stable and is enabled by default.
3278
Remove the empty "message" field from tracing events emitted via the internal-logs feature
Fix panic when calling Context::current() from Drop implementations triggered by ContextGuard cleanup (#3262).

`v0.31.0`

Compare Source

Released 2025-Sep-25

Breaking Change return type of opentelemetry::global::set_tracer_provider to Unit to align with metrics counterpart
Add get_all method to opentelemetry::propagation::Extractor to return all values of the given propagation key and provide a default implementation.
Add an IntoIterator implementation for opentelemetry::trace::TraceState to allow iterating through its key-value pair collection.

open-telemetry/opentelemetry-rust (opentelemetry-appender-tracing)

`v0.32.0`

Released 2026-May-08

Add tracing span attribute enrichment (experimental). When enabled,
attributes attached to active tracing spans are copied onto each emitted
log record. "Span" here refers to a tracing::span! from the
tracing crate (the appender's source), not an OpenTelemetry span.
#3482, #3505

Gated behind the new experimental_span_attributes cargo feature. As
with all experimental_* features in this repo, the API may change without
a major version bump until it is stabilized; once stable, the feature flag
will be removed.

Enrichment is disabled by default (no per-span overhead) and must be
opted into at runtime via a single builder method that accepts a
[TracingSpanAttributes] value:
```
use opentelemetry_appender_tracing::layer::TracingSpanAttributes;

// Copy all tracing-span attributes onto log records:
let layer = OpenTelemetryTracingBridge::builder(&provider)
    .with_tracing_span_attributes(TracingSpanAttributes::all())
    .build();

// Or copy only an allowlist of attributes:
let layer = OpenTelemetryTracingBridge::builder(&provider)
    .with_tracing_span_attributes(TracingSpanAttributes::allowlist(["session.id"]))
    .build();
```
Remove the experimental_use_tracing_span_context since
tracing-opentelemetry now supports activating the OpenTelemetry
context for the current tracing span. This fixes #3190 — the
circular dependency introduced by depending on tracing-opentelemetry
that depends on opentelemetry.
"spec_unstable_logs_enabled" feature flag is removed. The capability (and the
backing specification) is now stable and is enabled by default. #3278

`v0.31.1`

Released 2025-Oct-1

Bump tracing-opentelemetry to 0.32

`v0.31.0`

Released 2025-Sep-25

Updated opentelemetry dependency to version 0.31.0.

open-telemetry/opentelemetry-rust (opentelemetry-otlp)

`v0.32.0`

Compare Source

Released 2026-May-08

Add tls-provider-agnostic feature flag for environments that require a custom crypto backend (e.g., OpenSSL for FIPS compliance). Enables TLS code paths without bundling ring or aws-lc-rs.
Add build() directly on SpanExporterBuilder, MetricExporterBuilder, and LogExporterBuilder
(before selecting a transport), which auto-selects the transport based on the
OTEL_EXPORTER_OTLP_PROTOCOL environment variable or enabled features.
#3394
Breaking Removed ExportConfig, HasExportConfig, with_export_config(), HasTonicConfig, HasHttpConfig, TonicConfig, and HttpConfig from public API.
Use the public WithExportConfig, WithTonicConfig, and WithHttpConfig trait methods instead, which remain unchanged.
The gRPC/tonic OTLP exporter's build method now returns an error for all signals (traces, metrics, logs) when
an https:// endpoint is configured but no TLS feature (tls-ring or tls-aws-lc) is enabled, instead of
silently sending unencrypted traffic. When a TLS feature is enabled and an https:// endpoint is used without
an explicit .with_tls_config(), a default ClientTlsConfig is automatically applied.
#3182
Prevent auth tokens from leaking in export error messages. gRPC and HTTP
exporter errors no longer include potentially sensitive server responses
(e.g., authentication tokens echoed back). Error messages returned to SDK
processors contain only the gRPC status code or HTTP status code. Full
details are logged at DEBUG level only.
#3021
Surface pre-flight transport error details at ERROR level when grpc-tonic
OTLP export fails due to a local misconfiguration. When the returned
tonic::Status wraps a local transport error (invalid URL, connect failure,
DNS), its source chain (e.g., "transport error: invalid URI") is appended
to the returned error so SDK processors surface it at ERROR without
requiring DEBUG logging. Server-returned gRPC status messages remain
DEBUG-only to preserve the auth-token leak safeguards from
#3021.
#3331
Add support for per-signal protocol environment variables:
OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, OTEL_EXPORTER_OTLP_METRICS_PROTOCOL,
OTEL_EXPORTER_OTLP_LOGS_PROTOCOL. These allow configuring different transport protocols
per signal type. Signal-specific vars take precedence over generic OTEL_EXPORTER_OTLP_PROTOCOL.
The auto-select build() method on each exporter builder now respects the full priority chain:
signal-specific env var > generic env var > feature-based default.
Transport/protocol mismatch validation: HTTP transport returns InvalidConfig when gRPC protocol
is requested; gRPC transport returns InvalidConfig when an HTTP protocol is requested.
Breaking: Protocol::default() no longer consults the OTEL_EXPORTER_OTLP_PROTOCOL
environment variable. It now returns only the feature-based default (http-json > http-proto >
grpc-tonic). Protocol resolution from environment variables is handled internally by the
exporter builders. Users who relied on Protocol::default() to read env vars should use
Protocol::from_env() instead.
Add support for OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE environment variable
to configure metrics temporality. Accepted values: cumulative (default), delta,
lowmemory (case-insensitive). Programmatic .with_temporality() overrides the env var.
Fix NoHttpClient error when multiple HTTP client features are enabled by using priority-based selection (reqwest-client > hyper-client > reqwest-blocking-client). #2994
Add partial success response handling for OTLP exporters (traces, metrics, logs) per OTLP spec. Exporters now log warnings when the server returns partial success responses with rejected items and error messages. #865
Refactor internal-logs feature in opentelemetry-otlp to reduce unnecessary dependencies3191
Fixed [#2777](https://github.com/open-telemetry/opentelemetry rust/issues/2777) to properly handle shutdown_with_timeout() when using grpc-tonic.
Deprecate tls feature in favor of explicit tls-ring and tls-aws-lc features.
Migration: Replace tls with tls-ring (or tls-aws-lc). Users of tls-roots or tls-webpki-roots must now also enable one of these.
Prevent logging of header values in OTLP tonic exporter #3465

`v0.31.1`: opentelemetry-otlp 0.31.1

Compare Source

What's Changed

feat(OTLP): add tls-ring, tls-aws-lc, and tls-provider-agnostic feature flags [patch release v0.31.1] by @lalitb in #3426

Full Changelog: open-telemetry/opentelemetry-rust@v0.31.0...opentelemetry-otlp-0.31.1

`v0.31.0`

Compare Source

Released 2025-Sep-25

Update opentelemetry-proto and opentelemetry-http dependency version to 0.31.0
Add HTTP compression support with gzip-http and zstd-http feature flags
Add retry with exponential backoff and throttling support for HTTP and gRPC exporters
This behaviour is opt in via the experimental-grpc-retry and experimental-http-retry flags on this crate. You can customize the retry policy using the with_retry_policy on the exporter builders.

open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)

`v0.32.0`

Compare Source

Released 2026-May-08

`v0.31.0`

Compare Source

Released 2025-Sep-25

Update to v1.34.0 of the semantic conventions.

open-telemetry/opentelemetry-rust (opentelemetry_sdk)

`v0.32.0`

Compare Source

Released 2026-May-08

SimpleSpanProcessor now suppresses telemetry during export, preventing
telemetry-induced-telemetry feedback loops. This aligns with the existing
behavior in BatchSpanProcessor and SimpleLogProcessor.
Removed SimpleConcurrentLogProcessor and the experimental_logs_concurrent_log_processor
feature flag. The use cases it was designed for (ETW/user_events exporters) are
better served by modeling those exporters as processors directly.
Added Counter::bind() and Histogram::bind() SDK implementations that
return pre-bound measurement handles (BoundCounter<T>, BoundHistogram<T>).
Bound instruments resolve the attribute-to-aggregator mapping once at bind time
and cache the result, eliminating per-call HashMap lookups. View attribute
filtering is applied at bind time so the hot path stays free of per-call
attribute processing. Bound and unbound recordings with the same (post-view)
attribute set always aggregate into the same data point, including the empty
attribute set. Bound entries are never evicted during delta collection while
a handle exists — idle cycles produce no export but the tracker persists. If
bind() is called at the cardinality limit, the handle binds directly to
the overflow tracker — its writes stay on the same direct (no-lookup) hot
path and consistently land in the otel.metric.overflow=true bucket for
the lifetime of the handle. To recover a bound handle after delta collection
frees space, drop the existing handle and call bind() again. Gated behind
the experimental_metrics_bound_instruments feature flag. Benchmarks show
~28x speedup for counter operations and ~9x for histograms.
Delta metrics collection now uses in-place eviction instead of draining the
HashMap on every collect cycle. Stale attribute sets that received no measurements
since the last collection are evicted. Note: recovery from cardinality overflow
now requires 2 collect cycles — the first marks entries as stale, the second
evicts them.
Breaking The SDK testing feature is now runtime agnostic. #3407
- TokioSpanExporter and new_tokio_test_exporter have been renamed to TestSpanExporter and new_test_exporter.
- The following transitive dependencies and features have been removed: tokio/rt, tokio/time, tokio/macros, tokio/rt-multi-thread, tokio-stream, experimental_async_runtime
Store InstrumentationScope in Arc internally in SdkTracer, making tracer clones cheaper (Arc refcount increment instead of deep copy).
Add 32-bit platform support by using portable-atomic for AtomicI64 and AtomicU64 in the metrics module. This enables compilation on 32-bit ARM targets (e.g., armv5te-unknown-linux-gnueabi, armv7-unknown-linux-gnueabihf).
Aggregation enum and StreamBuilder::with_aggregation() are now stable and no longer require the spec_unstable_metrics_views feature flag.
Fix service.name Resource attribute fallback to follow OpenTelemetry
specification by using unknown_service:<process.executable.name> format when
service name is not explicitly configured. Previously, it only used
unknown_service.
Fix SpanExporter::shutdown() default timeout from 5 nanoseconds to 5 seconds.
Breaking SpanExporter trait methods shutdown, shutdown_with_timeout, and force_flush now take &self instead of &mut self for consistency with LogExporter and PushMetricExporter. Implementers using interior mutability (e.g., Mutex, AtomicBool) require no changes.
Added Resource::get_ref(&self, key: &Key) -> Option<&Value> to allow retrieving a reference to a resource value without cloning.
Breaking Removed the following public hidden methods from the SdkTracer #3227:
- id_generator, should_sample
Breaking Moved the following SDK sampling types from opentelemetry::trace to opentelemetry_sdk::trace #3277:
- SamplingDecision, SamplingResult
- These types are SDK implementation details and should be imported from opentelemetry_sdk::trace instead.
StreamBuilder::build() now rejects usize::MAX as a cardinality limit
with a validation error. #3506
Fix Histogram boundaries being ignored in the presence of views #3312
TracerProviderBuilder::with_sampler allows to pass boxed instance of ShouldSample [#3313][3313]
Fix ObservableCounter and ObservableUpDownCounter now correctly report only data points from the current measurement cycle, removing stale attribute combinations that are no longer observed. #3248
Fix panic when SpanProcessor::on_end calls Context::current() (#3262).
- Updated SpanProcessor::on_end documentation to clarify that Context::current() returns the parent context, not the span's context
Fix traceparent headers with unknown flags (e.g. W3C random-trace-id flag 0x02) being incorrectly rejected. Unknown flags are now accepted and zeroed out as required by the W3C trace-context spec. #3435
Breaking InMemoryExporterError has been removed and replaced by OTelSdkError, and a new JaegerRemoteSamplerBuildError introduced to replace last uses of TraceError. #3458
"spec_unstable_logs_enabled" feature flag is removed. The capability (and the
backing specification) is now stable and is enabled by default. #3278

`v0.31.0`

Compare Source

Released 2025-Sep-25

Updated opentelemetry and opentelemetry-http dependencies to version 0.31.0.
Feature: Add span flags support for isRemote property in OTLP exporter (#3153)
Updated span and link transformations to properly set flags field (0x100 for local, 0x300 for remote)
TODO: Placeholder for Span processor related things
- Fix SpanProcessor::on_start is no longer called on non recording spans
Fix: Restore true parallel exports in the async-native BatchSpanProcessor by honoring OTEL_BSP_MAX_CONCURRENT_EXPORTS (#2959). A regression in #2685 inadvertently awaited the export() future directly in opentelemetry-sdk/src/trace/span_processor_with_async_runtime.rs instead of spawning it on the runtime, forcing all exports to run sequentially.
Feature: Added Clone implementation to SdkLogger for API consistency with SdkTracer (#3058).
Fix: batch size accounting in BatchSpanProcessor when queue is full (#3089).
Fix: Resolved dependency issue where the "logs" feature incorrectly
required the "trace" feature flag
(#3096).
The logs functionality now operates independently, while automatic correlation
between logs and traces continues to work when the "trace" feature is
explicitly enabled.
Fix: Fix shutdown of SimpleLogProcessor and async BatchLogProcessor.
Default implementation of LogProcessor::shutdown_with_timeout() will now warn to encourage users to implement proper shutdown.

tokio-rs/tracing-opentelemetry (tracing-opentelemetry)

`v0.32.1`

Compare Source

Added

allow OpenTelemetry context access with SpanRef (#234)
add event-counting filtering layer for spans (#228)
publicly export SetParentError

Fixed

fix panic in multithreaded follows-from

Other

Remove unwanted dependency on opentelemetry sdk crate (#241)
update README.md links to use the latest version (#239)
remove thiserror and unused dependencies (#238)

`v0.32.0`

Compare Source

Added

Add configuration for including target in spans (#222)

Changed

OpenTelemetry context activation (#202)
- Trace ID and span ID can be obtained from OtelData via dedicated functions. Note that these
  will be available only if the context has already been built. (#233)
Correctly track entered and exited state for timings (#212)
Slightly improve error message on version mismatch (#211)
Remove Lazy for thread_local static (#215)
Update description of special fields and semantic conventions

Breaking Changes

The attributes code.filepath, code.lineno, and code.namespace have been renamed to
code.file.path, and code.line.number, and code.module.name, to align with the opentelemetry
semantic conventions for code. (#225)
Upgrade from opentelemetry to 0.31.0. Refer to the upstream
changelog
for more information. (#230)
Hold onto MetricsProvider in MetricsLayer (#224)
The attribute otel.status_message was changed to otel.status_description to align with the
opentelemetry semantic conventions for code. (#209)
Remove the metrics_gauge_unstable feature.

Configuration

📅 Schedule: (UTC)

Branch creation
- "before 4am every weekday,every weekend"
Automerge
- "before 4am every weekday,every weekend"

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

vercel · 2025-11-19T13:51:04Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ds-theme	Ready	Preview, Comment	May 23, 2026 1:16am
hash	Error		May 23, 2026 1:16am
hashdotdesign	Ready	Preview, Comment	May 23, 2026 1:16am
hashdotdesign-tokens	Ready	Preview, Comment	May 23, 2026 1:16am
petrinaut	Ready	Preview	May 23, 2026 1:16am

codecov · 2025-11-19T13:56:06Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.83%. Comparing base (f4d2137) to head (3931625).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8013   +/-   ##
=======================================
  Coverage   62.83%   62.83%           
=======================================
  Files        1368     1368           
  Lines      140845   140845           
  Branches     5859     5859           
=======================================
+ Hits        88502    88505    +3     
+ Misses      51412    51409    -3     
  Partials      931      931

Flag	Coverage Δ
local.claude-hooks	`0.00% <ø> (ø)`
local.harpc-client	`51.24% <ø> (ø)`
rust.antsi	`0.00% <ø> (ø)`
rust.error-stack	`90.87% <ø> (ø)`
rust.harpc-codec	`84.70% <ø> (ø)`
rust.harpc-net	`96.24% <ø> (+0.04%)`	⬆️
rust.harpc-tower	`67.03% <ø> (ø)`
rust.harpc-types	`0.00% <ø> (ø)`
rust.harpc-wire-protocol	`92.23% <ø> (ø)`
rust.hash-codec	`72.76% <ø> (ø)`
rust.hash-graph-authorization	`62.34% <ø> (ø)`
rust.hash-graph-temporal-versioning	`47.95% <ø> (ø)`
rust.hashql-core	`82.17% <ø> (ø)`
rust.hashql-diagnostics	`72.53% <ø> (ø)`
rust.hashql-syntax-jexpr	`94.06% <ø> (ø)`

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

cursor · 2026-01-12T11:45:06Z

PR Summary

Medium Risk
Upgrades core telemetry/tracing dependencies, which can subtly change span/context propagation and exporter behavior at runtime. While code changes are limited to dependency updates, regressions would impact observability across services.

Overview
Upgrades workspace OpenTelemetry crates to 0.32.0 (including opentelemetry, opentelemetry-otlp, opentelemetry_sdk, and semantic conventions) and updates tracing-opentelemetry to 0.32.0.

Refreshes Cargo.lock to match, pulling in newer transitive gRPC/protobuf pieces (e.g., tonic/prost, plus tonic-types) and updating related dependency resolution/version pins used by telemetry components.

^{Reviewed by Cursor Bugbot for commit 3931625. Bugbot is set up for automated code reviews on this repo. Configure here.}

codspeed-hq · 2026-01-22T12:58:39Z

Merging this PR will not alter performance

✅ 56 untouched benchmarks
⏩ 24 skipped benchmarks¹

_{Comparing deps/rs/opentelemetry-rust-crates (3931625) with main (f4d2137)}

24 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

cursor · 2026-03-31T17:13:23Z

 tracing-error                      = { version = "0.2.1", default-features = false }
 tracing-flame                      = { version = "0.2.0", default-features = false }
-tracing-opentelemetry              = { version = "0.31.0", default-features = false }
+tracing-opentelemetry              = { version = "0.32.0", default-features = false }


set_parent return type changed, unhandled Result breaks CI

High Severity

Upgrading tracing-opentelemetry from 0.31 to 0.32 changes OpenTelemetrySpanExt::set_parent return type from () to Result<(), SetParentError>. The call in libs/@local/graph/api/src/rest/http_tracing_layer.rs ignores this Result, which triggers an unused_must_use warning. Since the project runs clippy with -D warnings (in .justfile), this becomes a build failure. The Result needs to be explicitly handled or discarded.

Additional Locations (1)

Cargo.toml#L199-L204

cursor · 2026-04-29T11:47:36Z

 "tokio-util",
 "tracing",
- "tracing-opentelemetry",
+ "tracing-opentelemetry 0.31.0",


Duplicate OpenTelemetry versions break tarpc trace propagation

Medium Severity

The tarpc git dependency is pinned to opentelemetry 0.30.0 and tracing-opentelemetry 0.31.0, while the workspace now uses opentelemetry 0.31.0 and tracing-opentelemetry 0.32.1. Before this PR, all crates shared a single version. Now, two incompatible versions of tracing-opentelemetry coexist in the binary. Since OpenTelemetrySpanExt methods interact with span extension data (OtelData) by TypeId, tarpc's version 0.31.0 OtelData won't match the application layer's version 0.32.1 OtelData. This silently breaks trace context propagation across tarpc RPC calls used by the type fetcher service.

Additional Locations (1)

Cargo.lock#L9761-L9790

^{Reviewed by Cursor Bugbot for commit 5ad55e9. Configure here.}

cursor · 2026-05-12T17:03:22Z

+opentelemetry-appender-tracing     = { version = "0.31.0", default-features = false }
+opentelemetry-otlp                 = { version = "0.31.0", default-features = false }
+opentelemetry-semantic-conventions = { version = "0.31.0", default-features = false }
+opentelemetry_sdk                  = { version = "0.31.0", default-features = false }


OpenTelemetry version split breaks tarpc trace context propagation

Medium Severity

Updating the workspace opentelemetry to 0.31.0 and tracing-opentelemetry to 0.32.x introduces a version split because tarpc (pinned to a git revision) still depends on opentelemetry 0.30.0 and tracing-opentelemetry 0.31.0. Before this PR, all crates shared the same OpenTelemetry versions. Now two separate opentelemetry::global states exist — the app configures the 0.31.0 global (propagator, tracer provider), but tarpc operates on the unconfigured 0.30.0 global. Additionally, the tracing-opentelemetry 0.32.1 layer stores span extension data as its own types, which tarpc's 0.31.0 OpenTelemetrySpanExt calls can't retrieve. This silently breaks trace context propagation across tarpc RPC boundaries (the type-fetcher service).

Additional Locations (1)

Cargo.lock#L9038-L9051

^{Reviewed by Cursor Bugbot for commit 728c751. Configure here.}

github-actions · 2026-05-12T18:14:43Z

Benchmark results

@rust/hash-graph-benches – Integrations

policy_resolution_large

Function	Value	Mean	Flame graphs
resolve_policies_for_actor	user: empty, selectivity: high, policies: 2002	$$26.9 \mathrm{ms} \pm 170 \mathrm{μs}\left({\color{gray}-1.253 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: low, policies: 1	$$3.45 \mathrm{ms} \pm 17.2 \mathrm{μs}\left({\color{gray}-0.844 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: medium, policies: 1001	$$12.3 \mathrm{ms} \pm 74.2 \mathrm{μs}\left({\color{gray}0.224 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: high, policies: 3314	$$43.1 \mathrm{ms} \pm 362 \mathrm{μs}\left({\color{gray}2.84 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: low, policies: 1	$$14.8 \mathrm{ms} \pm 121 \mathrm{μs}\left({\color{gray}-0.597 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: medium, policies: 1526	$$23.5 \mathrm{ms} \pm 142 \mathrm{μs}\left({\color{gray}0.125 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: high, policies: 2078	$$28.1 \mathrm{ms} \pm 184 \mathrm{μs}\left({\color{gray}1.15 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: low, policies: 1	$$3.76 \mathrm{ms} \pm 17.0 \mathrm{μs}\left({\color{gray}-0.432 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: medium, policies: 1033	$$13.3 \mathrm{ms} \pm 114 \mathrm{μs}\left({\color{gray}0.716 \mathrm{\%}}\right) $$	Flame Graph

policy_resolution_medium

Function	Value	Mean	Flame graphs
resolve_policies_for_actor	user: empty, selectivity: high, policies: 102	$$3.73 \mathrm{ms} \pm 21.2 \mathrm{μs}\left({\color{gray}-0.563 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: low, policies: 1	$$2.93 \mathrm{ms} \pm 14.9 \mathrm{μs}\left({\color{gray}0.430 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: medium, policies: 51	$$3.30 \mathrm{ms} \pm 17.6 \mathrm{μs}\left({\color{gray}0.395 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: high, policies: 269	$$5.11 \mathrm{ms} \pm 26.3 \mathrm{μs}\left({\color{gray}0.604 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: low, policies: 1	$$3.46 \mathrm{ms} \pm 14.3 \mathrm{μs}\left({\color{gray}-0.007 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: medium, policies: 107	$$4.10 \mathrm{ms} \pm 25.9 \mathrm{μs}\left({\color{gray}1.50 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: high, policies: 133	$$4.37 \mathrm{ms} \pm 26.2 \mathrm{μs}\left({\color{gray}0.394 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: low, policies: 1	$$3.39 \mathrm{ms} \pm 15.8 \mathrm{μs}\left({\color{gray}-0.243 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: medium, policies: 63	$$4.01 \mathrm{ms} \pm 21.9 \mathrm{μs}\left({\color{gray}-0.108 \mathrm{\%}}\right) $$	Flame Graph

policy_resolution_none

Function	Value	Mean	Flame graphs
resolve_policies_for_actor	user: empty, selectivity: high, policies: 2	$$2.62 \mathrm{ms} \pm 13.7 \mathrm{μs}\left({\color{gray}0.232 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: low, policies: 1	$$2.45 \mathrm{ms} \pm 12.2 \mathrm{μs}\left({\color{gray}-0.260 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: medium, policies: 1	$$2.57 \mathrm{ms} \pm 12.4 \mathrm{μs}\left({\color{gray}-0.517 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: high, policies: 8	$$2.88 \mathrm{ms} \pm 16.6 \mathrm{μs}\left({\color{gray}0.706 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: low, policies: 1	$$2.67 \mathrm{ms} \pm 13.7 \mathrm{μs}\left({\color{gray}-0.381 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: medium, policies: 3	$$2.85 \mathrm{ms} \pm 15.7 \mathrm{μs}\left({\color{gray}-0.170 \mathrm{\%}}\right) $$	Flame Graph

policy_resolution_small

Function	Value	Mean	Flame graphs
resolve_policies_for_actor	user: empty, selectivity: high, policies: 52	$$2.95 \mathrm{ms} \pm 15.3 \mathrm{μs}\left({\color{gray}-0.325 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: low, policies: 1	$$2.67 \mathrm{ms} \pm 14.9 \mathrm{μs}\left({\color{gray}0.808 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: medium, policies: 25	$$2.92 \mathrm{ms} \pm 15.9 \mathrm{μs}\left({\color{gray}0.330 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: high, policies: 94	$$3.35 \mathrm{ms} \pm 17.9 \mathrm{μs}\left({\color{gray}0.596 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: low, policies: 1	$$2.88 \mathrm{ms} \pm 17.6 \mathrm{μs}\left({\color{gray}0.050 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: medium, policies: 26	$$3.18 \mathrm{ms} \pm 17.4 \mathrm{μs}\left({\color{gray}0.048 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: high, policies: 66	$$3.28 \mathrm{ms} \pm 18.6 \mathrm{μs}\left({\color{gray}0.293 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: low, policies: 1	$$2.85 \mathrm{ms} \pm 12.7 \mathrm{μs}\left({\color{gray}-1.180 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: medium, policies: 29	$$3.25 \mathrm{ms} \pm 17.1 \mathrm{μs}\left({\color{gray}0.138 \mathrm{\%}}\right) $$	Flame Graph

read_scaling_complete

Function	Value	Mean	Flame graphs
entity_by_id;one_depth	1 entities	$$53.8 \mathrm{ms} \pm 287 \mathrm{μs}\left({\color{gray}0.201 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;one_depth	10 entities	$$44.7 \mathrm{ms} \pm 178 \mathrm{μs}\left({\color{gray}-0.651 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;one_depth	25 entities	$$49.8 \mathrm{ms} \pm 219 \mathrm{μs}\left({\color{gray}0.942 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;one_depth	5 entities	$$43.9 \mathrm{ms} \pm 503 \mathrm{μs}\left({\color{lightgreen}-10.549 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;one_depth	50 entities	$$61.5 \mathrm{ms} \pm 306 \mathrm{μs}\left({\color{gray}0.980 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;two_depth	1 entities	$$60.6 \mathrm{ms} \pm 378 \mathrm{μs}\left({\color{gray}-0.241 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;two_depth	10 entities	$$54.4 \mathrm{ms} \pm 324 \mathrm{μs}\left({\color{gray}-0.616 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;two_depth	25 entities	$$102 \mathrm{ms} \pm 480 \mathrm{μs}\left({\color{gray}0.097 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;two_depth	5 entities	$$50.3 \mathrm{ms} \pm 2.57 \mathrm{ms}\left({\color{red}10.1 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;two_depth	50 entities	$$290 \mathrm{ms} \pm 1.09 \mathrm{ms}\left({\color{red}7.81 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;zero_depth	1 entities	$$19.1 \mathrm{ms} \pm 111 \mathrm{μs}\left({\color{gray}-0.860 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;zero_depth	10 entities	$$19.7 \mathrm{ms} \pm 96.4 \mathrm{μs}\left({\color{gray}1.43 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;zero_depth	25 entities	$$20.0 \mathrm{ms} \pm 132 \mathrm{μs}\left({\color{gray}0.450 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;zero_depth	5 entities	$$19.0 \mathrm{ms} \pm 93.5 \mathrm{μs}\left({\color{gray}1.58 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;zero_depth	50 entities	$$24.8 \mathrm{ms} \pm 144 \mathrm{μs}\left({\color{gray}-0.737 \mathrm{\%}}\right) $$	Flame Graph

read_scaling_linkless

Function	Value	Mean	Flame graphs
entity_by_id	1 entities	$$18.8 \mathrm{ms} \pm 106 \mathrm{μs}\left({\color{gray}-1.732 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10 entities	$$18.9 \mathrm{ms} \pm 81.0 \mathrm{μs}\left({\color{gray}-0.366 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	100 entities	$$19.0 \mathrm{ms} \pm 106 \mathrm{μs}\left({\color{gray}1.14 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	1000 entities	$$19.7 \mathrm{ms} \pm 112 \mathrm{μs}\left({\color{gray}-0.131 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10000 entities	$$26.7 \mathrm{ms} \pm 248 \mathrm{μs}\left({\color{gray}0.659 \mathrm{\%}}\right) $$	Flame Graph

representative_read_entity

Function	Value	Mean	Flame graphs
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/block/v/1`	$$34.0 \mathrm{ms} \pm 338 \mathrm{μs}\left({\color{gray}-1.363 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/book/v/1`	$$34.7 \mathrm{ms} \pm 326 \mathrm{μs}\left({\color{gray}1.06 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/building/v/1`	$$34.1 \mathrm{ms} \pm 315 \mathrm{μs}\left({\color{gray}1.03 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/organization/v/1`	$$34.2 \mathrm{ms} \pm 294 \mathrm{μs}\left({\color{gray}-3.949 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/page/v/2`	$$33.6 \mathrm{ms} \pm 309 \mathrm{μs}\left({\color{gray}-3.215 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/person/v/1`	$$33.2 \mathrm{ms} \pm 342 \mathrm{μs}\left({\color{gray}-2.430 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/playlist/v/1`	$$34.4 \mathrm{ms} \pm 316 \mathrm{μs}\left({\color{gray}-2.038 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/song/v/1`	$$33.7 \mathrm{ms} \pm 298 \mathrm{μs}\left({\color{gray}-4.279 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/uk-address/v/1`	$$32.7 \mathrm{ms} \pm 279 \mathrm{μs}\left({\color{lightgreen}-5.685 \mathrm{\%}}\right) $$	Flame Graph

representative_read_entity_type

Function	Value	Mean	Flame graphs
get_entity_type_by_id	Account ID: `bf5a9ef5-dc3b-43cf-a291-6210c0321eba`	$$8.32 \mathrm{ms} \pm 50.0 \mathrm{μs}\left({\color{gray}-0.169 \mathrm{\%}}\right) $$	Flame Graph

representative_read_multiple_entities

Function	Value	Mean	Flame graphs
entity_by_property	traversal_paths=0	0	$$91.8 \mathrm{ms} \pm 581 \mathrm{μs}\left({\color{gray}0.525 \mathrm{\%}}\right) $$
entity_by_property	traversal_paths=255	1,resolve_depths=inherit:1;values:255;properties:255;links:127;link_dests:126;type:true	$$144 \mathrm{ms} \pm 747 \mathrm{μs}\left({\color{gray}-0.229 \mathrm{\%}}\right) $$
entity_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:0;links:0;link_dests:0;type:false	$$97.8 \mathrm{ms} \pm 582 \mathrm{μs}\left({\color{gray}-0.492 \mathrm{\%}}\right) $$
entity_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:0;links:1;link_dests:0;type:true	$$109 \mathrm{ms} \pm 780 \mathrm{μs}\left({\color{gray}0.088 \mathrm{\%}}\right) $$
entity_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:2;links:1;link_dests:0;type:true	$$116 \mathrm{ms} \pm 635 \mathrm{μs}\left({\color{gray}0.359 \mathrm{\%}}\right) $$
entity_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:2;properties:2;links:1;link_dests:0;type:true	$$123 \mathrm{ms} \pm 549 \mathrm{μs}\left({\color{gray}-0.606 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=0	0	$$101 \mathrm{ms} \pm 565 \mathrm{μs}\left({\color{gray}-0.745 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=255	1,resolve_depths=inherit:1;values:255;properties:255;links:127;link_dests:126;type:true	$$130 \mathrm{ms} \pm 534 \mathrm{μs}\left({\color{gray}-0.506 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:0;links:0;link_dests:0;type:false	$$108 \mathrm{ms} \pm 496 \mathrm{μs}\left({\color{gray}-0.199 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:0;links:1;link_dests:0;type:true	$$117 \mathrm{ms} \pm 606 \mathrm{μs}\left({\color{gray}-0.445 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:2;links:1;link_dests:0;type:true	$$118 \mathrm{ms} \pm 513 \mathrm{μs}\left({\color{gray}-0.113 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:2;properties:2;links:1;link_dests:0;type:true	$$118 \mathrm{ms} \pm 488 \mathrm{μs}\left({\color{gray}-0.298 \mathrm{\%}}\right) $$

scenarios

Function	Value	Mean	Flame graphs
full_test	query-limited	$$190 \mathrm{ms} \pm 640 \mathrm{μs}\left({\color{red}6.58 \mathrm{\%}}\right) $$	Flame Graph
full_test	query-unlimited	$$181 \mathrm{ms} \pm 2.43 \mathrm{ms}\left({\color{red}19.6 \mathrm{\%}}\right) $$	Flame Graph
linked_queries	query-limited	$$39.9 \mathrm{ms} \pm 220 \mathrm{μs}\left({\color{gray}0.869 \mathrm{\%}}\right) $$	Flame Graph
linked_queries	query-unlimited	$$531 \mathrm{ms} \pm 809 \mathrm{μs}\left({\color{gray}-1.698 \mathrm{\%}}\right) $$	Flame Graph

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 4 total unresolved issues (including 3 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3931625. Configure here.}

cursor · 2026-05-23T01:13:59Z

 tracing-error                      = { version = "0.2.1", default-features = false }
 tracing-flame                      = { version = "0.2.0", default-features = false }
-tracing-opentelemetry              = { version = "0.31.0", default-features = false }
+tracing-opentelemetry              = { version = "0.32.0", default-features = false }


Incompatible opentelemetry and tracing-opentelemetry version pairing

High Severity

tracing-opentelemetry 0.32.x is compatible with opentelemetry 0.31.0, not 0.32.0. The lock file confirms tracing-opentelemetry 0.32.1 depends on opentelemetry 0.31.0, while the workspace specifies opentelemetry = "0.32.0". This creates two incompatible versions of opentelemetry in the dependency tree, causing type mismatches wherever project code passes opentelemetry 0.32.0 types (like Context or Tracer) to tracing-opentelemetry which expects opentelemetry 0.31.0 types. The correct pairing is tracing-opentelemetry = "0.33.0" with opentelemetry = "0.32.0".

^{Reviewed by Cursor Bugbot for commit 3931625. Configure here.}

hash-worker Bot enabled auto-merge November 5, 2025 00:34

hash-worker Bot assigned indietyp and TimDiekmann Nov 5, 2025

hash-worker Bot requested a review from a team November 5, 2025 00:34

github-actions Bot added the area/deps Relates to third-party dependencies (area) label Nov 5, 2025

vercel Bot deployed to Preview – hashdotdesign November 5, 2025 00:37 View deployment

vercel Bot deployed to Preview – hash November 5, 2025 00:47 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 2ab7c86 to 3750c33 Compare November 19, 2025 13:50

vercel Bot had a problem deploying to Preview – petrinaut November 19, 2025 13:51 Failure

vercel Bot deployed to Preview – hashdotdesign November 19, 2025 13:53 View deployment

vercel Bot deployed to Preview – hash November 19, 2025 14:03 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 3750c33 to 22383b2 Compare December 7, 2025 09:42

vercel Bot deployed to Preview – hashdotdesign December 7, 2025 09:46 View deployment

vercel Bot deployed to Preview – petrinaut December 7, 2025 09:47 View deployment

vercel Bot deployed to Preview – hash December 7, 2025 09:55 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 22383b2 to 56681d9 Compare January 12, 2026 11:45

vercel Bot deployed to Preview – hashdotdesign January 12, 2026 11:48 View deployment

vercel Bot deployed to Preview – petrinaut January 12, 2026 11:50 View deployment

vercel Bot deployed to Preview – hash January 12, 2026 11:59 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 56681d9 to 1574cf8 Compare January 22, 2026 12:54

vercel Bot deployed to Preview – ds-theme January 22, 2026 12:57 View deployment

vercel Bot deployed to Preview – hashdotdesign January 22, 2026 12:57 View deployment

vercel Bot deployed to Preview – petrinaut January 22, 2026 12:58 View deployment

vercel Bot deployed to Preview – hash January 22, 2026 13:07 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 1574cf8 to 296ff99 Compare February 17, 2026 09:26

vercel Bot deployed to Preview – hashdotdesign-tokens February 17, 2026 09:29 View deployment

vercel Bot deployed to Preview – petrinaut March 31, 2026 17:09 View deployment

cursor Bot reviewed Mar 31, 2026

View reviewed changes

vercel Bot deployed to Preview – hash March 31, 2026 17:19 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 742ff19 to 1d7c806 Compare April 2, 2026 18:31

vercel Bot deployed to Preview – hashdotdesign-tokens April 2, 2026 18:33 View deployment

vercel Bot deployed to Preview – hashdotdesign April 2, 2026 18:34 View deployment

vercel Bot deployed to Preview – petrinaut April 2, 2026 18:35 View deployment

vercel Bot deployed to Preview – hash April 2, 2026 18:45 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 1d7c806 to 5ad55e9 Compare April 29, 2026 11:42

vercel Bot deployed to Preview – hashdotdesign-tokens April 29, 2026 11:45 View deployment

vercel Bot deployed to Preview – petrinaut April 29, 2026 11:46 View deployment

cursor Bot reviewed Apr 29, 2026

View reviewed changes

vercel Bot deployed to Preview – hash April 29, 2026 11:55 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 5ad55e9 to 13a7a31 Compare May 5, 2026 11:09

vercel Bot deployed to Preview – hashdotdesign-tokens May 5, 2026 11:12 View deployment

vercel Bot deployed to Preview – petrinaut May 5, 2026 11:13 View deployment

vercel Bot deployed to Preview – hash May 5, 2026 11:22 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 13a7a31 to 728c751 Compare May 12, 2026 16:57

vercel Bot deployed to Preview – hashdotdesign-tokens May 12, 2026 17:00 View deployment

vercel Bot deployed to Preview – petrinaut May 12, 2026 17:01 View deployment

cursor Bot reviewed May 12, 2026

View reviewed changes

vercel Bot deployed to Preview – hash May 12, 2026 17:13 View deployment

Update opentelemetry Rust crates to 0.32.0

3931625

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 728c751 to 3931625 Compare May 23, 2026 01:09

hash-worker Bot changed the title ~~Update opentelemetry Rust crates~~ Update opentelemetry Rust crates to 0.32.0 May 23, 2026

vercel Bot deployed to Preview – hashdotdesign-tokens May 23, 2026 01:12 View deployment

vercel Bot deployed to Preview – petrinaut May 23, 2026 01:13 View deployment

cursor Bot reviewed May 23, 2026

View reviewed changes

vercel Bot had a problem deploying to Preview – hash May 23, 2026 01:16 Failure

Conversation

hash-worker Bot commented Nov 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v0.31.1: opentelemetry-otlp 0.31.1

What's Changed

Added

Fixed

Other

Added

Changed

Breaking Changes

Configuration

Uh oh!

vercel Bot commented Nov 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov Bot commented Nov 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

cursor Bot commented Jan 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary

Uh oh!

codspeed-hq Bot commented Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merging this PR will not alter performance

Footnotes

Uh oh!

cursor Bot Mar 31, 2026

Choose a reason for hiding this comment

set_parent return type changed, unhandled Result breaks CI

Uh oh!

cursor Bot Apr 29, 2026

Choose a reason for hiding this comment

Duplicate OpenTelemetry versions break tarpc trace propagation

Uh oh!

cursor Bot May 12, 2026

Choose a reason for hiding this comment

OpenTelemetry version split breaks tarpc trace context propagation

Uh oh!

github-actions Bot commented May 12, 2026

Benchmark results

@rust/hash-graph-benches – Integrations

policy_resolution_large

policy_resolution_medium

policy_resolution_none

policy_resolution_small

read_scaling_complete

read_scaling_linkless

representative_read_entity

representative_read_entity_type

representative_read_multiple_entities

scenarios

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor Bot May 23, 2026

Choose a reason for hiding this comment

Incompatible opentelemetry and tracing-opentelemetry version pairing

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

2 participants

hash-worker Bot commented Nov 5, 2025 •

edited

Loading

`v0.31.1`: opentelemetry-otlp 0.31.1

vercel Bot commented Nov 19, 2025 •

edited

Loading

codecov Bot commented Nov 19, 2025 •

edited

Loading

cursor Bot commented Jan 12, 2026 •

edited

Loading

codspeed-hq Bot commented Jan 22, 2026 •

edited

Loading

`set_parent` return type changed, unhandled Result breaks CI