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 }}
Repository navigation
Segment context not propagated when asyncio.run_in_executor is used #446
cannot find the current segment/subsegment, please make sure you have a segment open
No segment found, cannot begin subsegment s3.
cannot find the current segment/subsegment, please make sure you have a segment open
cannot find the current segment/subsegment, please make sure you have a segment open
No segment to end
cannot find the current segment/subsegment, please make sure you have a segment open
I understand from the README that when using a thread pool (which is the default executor), the trace entity needs to be manually propagated. Could it be propagated automatically?
I'm asking because in the use case I have, a 3rd party library I'm using is making the call so I couldn't patch the call sites easily.
Reacted by HJustin, Amit Vikram Raj, John Williams, Rodrigo Mafra and Henry Chladil
Activity
amitvikramraj commentedon Nov 13, 2024
Hi,
Today, while working with xray, I stumbled upon this library; haven't tried it; I'm not sure, but it looks like it might solve your problem!
henrycjc commentedon Nov 30, 2025
Having the same issue - has anyone found a workaround?