Steven Davidovitz

It can take some time for changes to propagate for cloud load balancers, so flagger should ensure the route changes are current before proceeding with any more. I'm not considering...

pubsub: concurrent map write panic when publishing with telemetry enabled and shared attributes

1

## Client PubSub ## Environment ``` $ go version go version go1.23.4 darwin/arm64 ``` ## Code and Dependencies ```go package main import ( "context" "fmt" "sync" "strings" "cloud.google.com/go/pubsub" "go.opentelemetry.io/otel" "go.opentelemetry.io/otel/exporters/otlp/otlptrace"...

feat: add valuable serialization support to appender-tracing

1

Fixes https://github.com/open-telemetry/opentelemetry-rust/issues/2819 Design discussion issue (if applicable) _N/A_ ## Changes Supports the `valuable` extension to `tracing` for appender-tracing. I moved the `serde::Serialize` extension out of appender-log into the main package...