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
Fix Sentry child span capture by binding Hub correctly (#12284)
The root cause was that `with_sentry_transaction()` created a new Hub
with the transaction context, but then in `worker.rs` the code called
`.bind_hub(Hub::current())` which bound the future to the original Hub
instead of the new one. This meant all child tracing spans were
attached to the wrong Hub that lacked the transaction context, so
Sentry never saw them as children of the transaction.
The fix moves the `.bind_hub(hub)` call inside `with_sentry_transaction()`
so the callback future executes with the correct Hub that has the
transaction, ensuring all child spans are properly associated with
the parent transaction.
0 commit comments