o i7+ @shdZddlZddlZddlZddlZddlZddlmZmZddl m Z ddl m Z m Z ddlmZddlmZddlmZdd lmZdd lmZmZmZddlmZdd lmZmZejd Zd Zde fddZ!deeddeedddde!r~dndej"ej#diddgej"ddidddZ$e dede%deddfd d!Z&e dede%deddfd"d#Z'e dede%deddfd$d%Z(ed&Z)d'e)de fd(d)Z*Gd*d+d+eZ+e+j,e+j-e+j.d,Z/dAd-d.Z0d/e%de+fd0d1Z1e ej2fd2e3dededffd3d4Z4d5eded6fd7d8Z5e0ej"d9kre6d:7ej8e1e9Z:dBd;d<Z;dBd=e%d>e%dBfd?d@Z)rAr0r1rArNcG"t|sdSt||g|RdS)z~ As [`debug`][logging.Logger.debug], but subsequent calls with the same message are silently dropped. N)rEr8selfr0rAr1rrr debug_oncewz_VllmLogger.debug_oncecGrG)z| As [`info`][logging.Logger.info], but subsequent calls with the same message are silently dropped. N)rEr;rHrrr info_oncesz_VllmLogger.info_oncecGrG)z As [`warning`][logging.Logger.warning], but subsequent calls with the same message are silently dropped. N)rEr=rHrrr warning_oncerKz_VllmLogger.warning_once) __name__ __module__ __qualname____doc__strrLogScoperJrLrMrrrrrFns.   rF)rJrLrMcCs8tttttftBf}tjstjrtdtjr@t}|dd}tj|d<tj |d<t r1dnd|d<|dd}tj|d<tjr|t tjsOtd tjt tjd d }t|}Wdn1shwYt|tsztd t|j|}|d iD] }|ddkrd|d<q|rt|dSdS)NzVLLM_CONFIGURE_LOGGING evaluated to false, but VLLM_LOGGING_CONFIG_PATH was given. VLLM_LOGGING_CONFIG_PATH implies VLLM_CONFIGURE_LOGGING. Please enable VLLM_CONFIGURE_LOGGING or unset VLLM_LOGGING_CONFIG_PATH.r(r#r&r'r$r%r,z6Could not load logging config. File does not exist: %szutf-8)encodingz.Invalid logging config. Expected dict, got %s.r+r zvllm.logging.NewLineFormatterr)dictrRr rVLLM_CONFIGURE_LOGGINGVLLM_LOGGING_CONFIG_PATH RuntimeErrorDEFAULT_LOGGING_CONFIGVLLM_LOGGING_LEVELrrr existsopenjsonloadsread isinstance ValueErrortyperNgetvaluesr)logging_config vllm_handler vllm_loggersfile custom_configr%rrr_configure_vllm_root_loggersF         rjnamecCs8t|}tD] \}}t||t||q tt|S)zThe main purpose of this function is to ensure that loggers are retrieved in such a way that we can be sure the root vllm logger has already been configured.)logging getLogger_METHODS_TO_PATCHitemssetattrr r rF)rkr/ method_namemethodrrr init_loggers  rsr&ccs*tjjj}t|dVt|dSN)rlrootmanagerdisable)r& current_levelrrrsuppress_loggings   rylgr)colornewlineNcCsf|dur1|jr*t|jdkr*|jdjdkr*|jdj}t|tr#dSt|tr*dS|j}|dusdS)Nr*rr#r{r|)r(lenrkr%r`rrparent)rzr%rrrcurrent_formatter_types$   rINFOhttpxcCs.|dvr|jj}|j}|jj}||sdSzq|j}|dur*|jj} |j} |jj} nd} d} d} t|dI} tj d} |dkr]| | d|d|d |d | d| d | d n| | d |d|d |d | d| d | d Wdn1swYWn t yYnwt t ||S)N)callrraz%Y-%m-%d %H:%M:%S.%frz Call to z in :z from  z Return from z to )f_code co_filenamef_linenoco_name startswithf_backr\datetimenowstrftimewrite NameErrorr _trace_calls)log_pathroot_dirframeeventargfilenamelineno func_name last_frame last_filename last_linenolast_func_nameftsrrrrsn     r log_file_pathrcCsHtdtd||durtjtjt}tt t ||dS)a Enable tracing of every function call in code under `root_dir`. This is useful for debugging hangs or crashes. `log_file_path` is the path to the log file. `root_dir` is the root directory of the code to trace. If None, it is the vllm root directory. Note that this call is thread-level, any threads calling this function will have the trace enabled. Other threads will not be affected. zVLLM_TRACE_FUNCTION is enabled. It will record every function executed by Python. This will slow down the code. It is suggested to be used for debugging hang or crashes only.zTrace frame log is saved to %sN) r/r<r:osr dirname__file__rsettracerr)rrrrrenable_trace_function_call(s  r)rNrt)=rQrr]rlrrcollections.abcrr contextlibr functoolsrrrlogging.configrr typesr typingr r r vllm.envsrvllm.logging_utilsrrVLLM_LOGGING_PREFIX_FORMAT _DATE_FORMATboolrrZrrYrRr8r;r=rSrErFrJrLrMrnrjrsrintryrrmsetLevelWARNINGrNr/rrrrrrs          "+ 0 $  +