U Ӈg@sddlZddlZddlZddlZddlZddlZddlZddlZddl Z ddlm Z ddl m Z ddl mZdZdZejdZGdd d ejZejdfd d Zd d ZddddZdddZGdddejZddZddZGdddejZddZdS)N) defaultdict)suppress) DefaultDictz6%(asctime)s - %(filename)s[%(levelname)s]: %(message)s#c@s eZdZdZddZddZdS)CustomLoggerTypezA hack to get mypy to stop complaining about custom logging methods. When using deprecated or trace logging, rather than: LOG = logging.getLogger(__name__) Instead do: LOG = cast(CustomLoggerType, logging.getLogger(__name__)) cOsdSNselfargskwargsr r 7/usr/lib/python3/dist-packages/cloudinit/log/loggers.pytrace&szCustomLoggerType.tracecOsdSrr r r r r deprecated)szCustomLoggerType.deprecatedN)__name__ __module__ __qualname____doc__rrr r r rrsrcCsN|p tt}t}ttj}||||| |||dSr) logging FormatterDEFAULT_LOG_FORMAT getLogger StreamHandlersysstderr setFormattersetLevel addHandler)levelZ formatterrootZconsoler r rsetup_basic_logging-s    r!c CsJ|sdS|jD],}t|tjrtt|W5QRXqt|jdSr) handlers isinstancerrrIOErrorflush flush_loggersparent)r hr r rr&7s   r&)returncCsHdd}ttdttdttjd|tttjd|tdS)z:Add DEPRECATED and TRACE log levels to the logging module.csfdd}|S)Ncs |r|j||f|dSr)Z isEnabledForZ_log)r messager r rr r log_at_levelEs z>define_extra_loggers..new_logger..log_at_levelr )rr,r r+r new_loggerDs z(define_extra_loggers..new_logger DEPRECATEDTRACErrN)rZ addLevelNamer.r/setattrLogger)r-r r rdefine_extra_loggersAs   r2c Csd|si}t}t}|tjg}|d}|rNt|trN|t|nhd|kr|dD]V}t|trx||q^t|t j j rdd|D}|d |q^|t|q^d}|D]b}t tP|d7}|drtj|st|}tj|||W5QRdSQRXq|||d d }tjd ||r`tjd tdS) NZlogcfglog_cfgscSsg|] }t|qSr )str).0cr r r esz!setup_logging.. r/Z log_basicTz0WARN: no logging configured! (tried %s configs) zSetting up basic logging... )rr LogExporterrWARNgetr#r4append collectionsabcIterablejoinrFileNotFoundError startswithospathisfileioStringIOZconfigZ fileConfigrrrwriter!) ZcfgZ root_loggerZexporterr3Zlog_cfgZa_cfgZcfg_strZam_triedZ basic_enabledr r r setup_loggingQsD            rKc@sNeZdZUeeZeeefed<e j dddZ ddZ ddZ d d Zd S) r;holderrecordcCs|j|j|dSr)rLZ levelnamer>Z getMessager rNr r remitszLogExporter.emitcCs t|jSr)copydeepcopyrLr r r r export_logsszLogExporter.export_logscCstt|_dSr)rlistrLrSr r r clean_logsszLogExporter.clean_logscCsdSrr rSr r rr%szLogExporter.flushN)rrrrrUrLrr4__annotations__r LogRecordrPrTrVr%r r r rr;s r;cCsFt}t|j}|D]}||||q|tjdS)z0Remove all current handlers and unset log level.N) rrrUr"r%closeZ removeHandlerrZNOTSET)logr"r(r r r reset_loggings  r[csJttjtdddtdfdd}ttjd|dS)zIn the event that internal logging exception occurs and logging is not possible for some reason, make a desperate final attempt to log to stderr which may ease debugging. handleErrorcSsdSrr rMr r rz&setup_backup_logging..z@FALLBACK: %(asctime)s - %(filename)s[%(levelname)s]: %(message)sc s*tt|W5QRXdS)z;A closure that emits logs on stderr when other methods failN)rr$Zhandler%rOZfallback_handlerr rr\s  z)setup_backup_logging..handleErrorN)rrrrr0rrZHandler)r\r r_rsetup_backup_loggings  r`cs eZdZdZfddZZS)CloudInitLogRecordzreporting the filename as __init__.py isn't very useful in logs if the filename is __init__.py, use the parent directory as the filename cs4tj||d|jkr0tjtj|j|_dS)Nz __init__.py)super__init__filenamerErFbasenamedirnamepathnamer  __class__r rrcs zCloudInitLogRecord.__init__)rrrrrc __classcell__r r rhrrasracCsJtjtj_tttt}| tj t |t tdS)z(Customize the root logger for cloud-initN)timegmtimerrZ converterr2r`r[r;rr<rrZsetLogRecordFactoryra)Zhandlerr r rconfigure_root_loggers  rm)N) Zcollections.abcr?rQrHrZlogging.configZlogging.handlersrErrkr contextlibrtypingrrr.DEBUGr/r1rr!r&r2rKrr;r[r`rXrarmr r r r s0       A