U Jc] @sUdZddlZddlZddlZddlZddlZddlmZddlm Z m Z ddl m Z ddl mZmZmZmZmZiae eejfed<deejd d d Zdeedd ddZeddddZdeeeeee eee ee edd ddZdS)aH Module contains events processing mechanisms that are integrated with the standard python logging. Example of usage: :: from torch.distributed.elastic import events event = events.Event(name="test_event", source=events.EventSource.WORKER, metadata={...}) events.get_logging_handler(destination="console").info(event) N)Enum)DictOptional)get_logging_handler)EventEventMetadataValue EventSource NodeState RdzvEvent_events_loggersnull) destinationreturncCsT|tkrLtd|}|tjddd|_t|}| ||t|<t|S)a Constructs python logger based on the destination type or extends if provided. Available destination could be found in ``handlers.py`` file. The constructed logger does not propagate messages to the upper level loggers, e.g. root logger. This makes sure that a single event can be processed once. Args: destination: The string representation of the event handler. Available handlers found in ``handlers`` module ztorchelastic-events-ZLOGLEVELINFOF) r logging getLoggersetLevelosenvironget propagater addHandler)rZ_events_loggerZlogging_handlerrM/tmp/pip-unpacked-wheel-gikjz4vx/torch/distributed/elastic/events/__init__.py_get_or_create_logger*s  r)eventrrcCst||dS)Nrinfo serialize)rrrrrrecordFsr )rrcCstd|dS)Ndynamic_rendezvousr)rrrrrecord_rdzv_eventIsr") run_idmessage node_statenamehostnamepidmaster_endpointlocal_idrankrc  CsttdtjrdS|s t}|s,t}t } d} t | dkrd| d} tj | j } |sd| j}~ |tjkrzt} nd} t| d|||||||||| d } t| dS)Nr!Zno_filerr#:) r'r$r%r(r)r&r*r,r+ error_trace) isinstancerr NullHandlersocketgetfqdnrgetpidinspectstacklenpathbasenamefilenamefunctionr ZFAILED traceback format_excr r")r$r%r&r'r(r)r*r+r,Z callstackr9Z stack_depth_1r.rrrrconstruct_and_record_rdzv_eventMs<     r=)r )r )r#r#Nr#NN)__doc__r4rrr1r;enumrtypingrrZ)torch.distributed.elastic.events.handlersrapirrr r r r strLogger__annotations__rr r"intr=rrrr s>