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
I believe #677 (comment) caused Context propagation to break.
This is a bit hard to detect since a link is created if the execution is within a span, but it links to the parent span rather than the span newly created
But that's when I realized that the current context is never set.
Instead, I think OpenTelemetry::Instrumentation::ActiveJob::Handlers::Default#start needs to add the the current Context stack and for finish_span to pop it.
Actually, the issue is that the context is set before injecting it in job.__otel_headers, so the parent context ends up being injected.
Description of the bug
I believe #677 (comment) caused Context propagation to break.
This is a bit hard to detect since a link is created if the execution is within a span, but it links to the parent span rather than the span newly created
Share details about your runtime
Operating system details: Linux, Ubuntu 20.04 LTS
RUBY_ENGINE: "ruby"
RUBY_VERSION: "3.3.4"
RUBY_DESCRIPTION: "ruby 3.3.4 (2024-07-09 revision be1089c8ec) [arm64-darwin23]"
Share a simplified reproduction if possible
The text was updated successfully, but these errors were encountered: