pubsub: concurrent map write panic when publishing with telemetry enabled and shared attributes #11314
Labels
api: pubsub
Issues related to the Pub/Sub API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Client
PubSub
Environment
Code and Dependencies
go.mod
Expected behavior
The answer could be that users should not be passing in a shared map of attributes, but I expected that any modification would only occur on a pubsub-local copy of the attributes.
Actual behavior
Full stacktrace: https://gist.github.com/steved/55a4c8a2aa451cd2246f1b752e9e44e6
It doesn't seem to be captured all the time, but I believe it's going through:
https://github.com/googleapis/google-cloud-go/blob/pubsub/v1.45.3/pubsub/trace.go#L304
https://github.com/open-telemetry/opentelemetry-go/blob/v1.33.0/propagation/trace_context.go#L64
The text was updated successfully, but these errors were encountered: