o i@sddlZddlmZddlmZddlmZddlmZejdk Z e r9ddl m Z ddl m Z Gd d d eZ nGd d d eZ d d Ze ZdS)N)IOLoop)BaseContextProvider)DefaultContextProvider)Span)r)StackContextInconsistentError)_statecspeZdZdZddZddZddZdd Zd d Zd d Z fddZ ddZ fddZ fddZ ZS)TracerStackContexta A context manager that manages ``Context`` instances in a thread-local state. It must be used every time a Tornado's handler or coroutine is used within a tracing Context. It is meant to work like a traditional ``StackContext``, preserving the state across asynchronous calls. Every time a new manager is initialized, a new ``Context()`` is created for this execution flow. A context created in a ``TracerStackContext`` is not shared between different threads. This implementation follows some suggestions provided here: https://github.com/tornadoweb/tornado/issues/1063 cCst|d|_dSN)r__init___contextselfrb/home/ubuntu/.local/lib/python3.10/site-packages/ddtrace/contrib/internal/tornado/stack_context.pyr s  zTracerStackContext.__init__cCdSzM Required to preserve the ``StackContext`` protocol. Nrr rrrenter(zTracerStackContext.entercCrrr)rtypevalue tracebackrrrexit.rzTracerStackContext.exitcCs*tj|_|jd|f|f|_|jt_|S)Nr)rcontexts old_contexts new_contextsr rrr __enter__4sTracerStackContext.__enter__cCs*tj}|jt_||jurtdd|_dS)Nz]stack_context inconsistency (may be caused by yield within a "with TracerStackContext" block))rrrrr)rrrrfinal_contextsrrr__exit__:s  TracerStackContext.__exit__cCsttjddduS)z5Helper to determine if we are currently in an IO loopinstanceN)getattrr_currentr rrr _has_io_loopFszTracerStackContext._has_io_loopcs"|s tt|S|duS)z7Helper to determine if we have an active context or notN)r$superr _has_active_context_get_state_active_contextr  __class__rrr&Js z&TracerStackContext._has_active_contextcCsJttjdD]}t||jr"|j}t|tr||S|SqdS)zFHelper to get the currently active context from the TracerStackContextrN)reversedrr isinstancer)r r_update_active)rstackctxrrrr'Rs  z,TracerStackContext._get_state_active_contextcs|s tt|S|S)aa Return the ``Context`` from the current execution flow. This method can be used inside a Tornado coroutine to retrieve and use the current tracing context. If used in a separated Thread, the `_state` thread-local storage is used to propagate the current Active context from the `MainThread`. )r$r%r activer'r r(rrr/]szTracerStackContext.activecsF|stt|||SttjdD] }t||jr ||_ q|S)a> Set the active ``Context`` for this async execution. If a ``TracerStackContext`` is not found, the context is discarded. If used in a separated Thread, the `_state` thread-local storage is used to propagate the current Active context from the `MainThread`. r) r$r%r activater*rrr+r)r )rr. stack_ctxr(rrr0ms zTracerStackContext.activate)__name__ __module__ __qualname____doc__r rrrrr$r&r'r/r0 __classcell__rrr(rr s  r c@seZdZddZddZdS)r cCdSr rr rrrrrcGr7r r)rexcrrrrr8r N)r2r3r4rrrrrrr s cOs8t||i|WdS1swYdS)z Run the given function within a traced StackContext. This function is used to trace Tornado web handlers, but can be used in your code to trace coroutines execution. N)r )funcargskwargsrrrrun_with_trace_contexts $r=)tornadotornado.iolooprddtrace._trace.providerrr ddtrace.tracer version_info_USE_STACK_CONTEXTtornado.stack_contextrrr r=context_providerrrrrs       p