You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 23, 2021. It is now read-only.
I think the description is incorrect or I misunderstood it (in which case I'd like to fix it on my side).
publicprotocolSpan{
/// The read-only `BaggageContext` of this `Span`, set when starting this `Span`.
varcontext:BaggageContext{get}
// ...
}
The way I understand it, the value of span.contex is not the same as the context passed when creating (starting) the span.
It should propagate whatever was in the context BUT update the trace context (parent id).
Related question (separate issue?) is if NoOpSpan should propagate context.
On my side NoOpSegment does not record anything but pass along the context, NoOpSpan returns empty baggage: