o +ke#@s|dZddlZddlZddlZddlZddlZddlZddlZdadddZ ddd Z d d Z dd d Z Gdddej ZdS)alogging facilities The way to use this is as follows: * each module declares its own logger, using: from .logger import create_logger logger = create_logger() * then each module uses logger.info/warning/debug/etc according to the level it believes is appropriate: logger.debug('debugging info for developers or power users') logger.info('normal, informational output') logger.warning('warn about a non-fatal error or sth else') logger.error('a fatal error') ... and so on. see the `logging documentation `_ for more information * console interaction happens on stderr, that includes interactive reporting functions like `help`, `info` and `list` * ...except ``input()`` is special, because we can't control the stream it is using, unfortunately. we assume that it won't clutter stdout, because interaction would be broken then anyways * what is output on INFO level is additionally controlled by commandline flags NFcCs2|d|d|jd|}tt}||dS)N:z: )__name__ create_loggerwarning)messagecategoryfilenamelinenofilelinemsgloggerr/usr/lib/python3.10/site-packages/borg/logger.py _log_warning/srBORG_LOGGING_CONFinfoc Csd}|r tj||}|rbz>tj|}t|}tj|Wdn1s)wYda t t }t d} || _ | d|dtt_WdStya} z t| }WYd} ~ nd} ~ wwt d}t|} |rs|ssd} nd} |r{t| nt| } | | t d} | | _|| _ t r|jr|jd |j|| ||da t t }|r|d |d |d | d tt_| S)asetup logging module according to the arguments provided if conf_fname is given (or the config file name can be determined via the env_var, if given): load this logging configuration. otherwise, set up a stream handler logger on stderr (by default, if no stream is provided). if is_serve == True, we configure a special log format as expected by the borg client log message interceptor. NTborgz'using logging configuration read from ""z/$LOG %(levelname)s %(name)s Remote: %(message)sz %(message)srzsetup_logging for "z" failed with "z".z,using builtin fallback logging configuration)osenvirongetpathabspathopenloggingconfigZ fileConfig configured getLoggerrjsondebugrwarnings showwarning Exceptionstr StreamHandler JsonFormatter Formatter setFormatter formatterhandlerscloseclear addHandlersetLevelupperr)streamZ conf_fnameZenv_varlevelZis_server err_msgfr Z borg_loggererrhandlerfmtr*rrr setup_logging8sT              r8cCshz(tj}t|}|dus|jtkr%|j}t|}|dus|jtks|jWSty3tYSw)zfind the name of the first module calling this module if we cannot find it, we return the current module's name (__name__) instead. N)inspect currentframef_back getmodulerAttributeError)framemodulerrrfind_parent_modulews    r@csGfddd|S)alazily create a Logger object with the proper path, which is returned by find_parent_module() by default, or is provided via the commandline this is really a shortcut for: logger = logging.getLogger(__name__) we use it to avoid errors and provide a more standard API. We must create the logger lazily, because this is usually called from module level (and thus executed at import time - BEFORE setup_logging() was called). By doing it lazily we can do the setup first, we just have to be careful not to call any logger methods before the setup_logging() call. If you try, you'll get an exception. csneZdZdddZeddZfddZdd Zd d Zd d Z ddZ ddZ ddZ ddZ ddZdS)z!create_logger..LazyLoggerNcSs|pt|_d|_dSN)r@_LazyLogger__name_LazyLogger__real_logger)selfnamerrr__init__s  z*create_logger..LazyLogger.__init__cSsP|jdur%ts tdt|j|_|jdr%|jjtjkr%|j d|jS)Nz8tried to call a logger before setup_logging() was calledz borg.debug.WARNING) rCrr$rrrB startswithr2NOTSETr/)rDrrrZ__loggers  z*create_logger..LazyLogger.__loggercs|jd|S)N.)rB)rDsuffix LazyLoggerrrgetChildz*create_logger..LazyLogger.getChildc_s|jj|i|SrA)_LazyLogger__loggerr/rDargskwrrrr/rOz*create_logger..LazyLogger.setLevelc_0d|vr|d|did<|jj|i|SNmsgidextra)pop setdefaultrPlogrQrrrrZz%create_logger..LazyLogger.logc_rTrU)rXrYrP exceptionrQrrrr\r[z+create_logger..LazyLogger.exceptionc_rTrU)rXrYrPr!rQrrrr!r[z'create_logger..LazyLogger.debugc_rTrU)rXrYrPrrQrrrrr[z&create_logger..LazyLogger.infoc_rTrU)rXrYrPrrQrrrrr[z)create_logger..LazyLogger.warningc_rTrU)rXrYrPerrorrQrrrr]r[z'create_logger..LazyLogger.errorc_rTrU)rXrYrPcriticalrQrrrr^r[z*create_logger..LazyLogger.criticalrA)r __module__ __qualname__rFpropertyrPrNr/rZr\r!rrr]r^rrLrrrMs    rMr)rErrLrrs8rcs eZdZdZfddZZS)r') levelnamerErrVcsJt|d|jddd}|jD]}t||d}|r|||<qt|S)NZ log_messagerCRITICAL)typetimerrb)superformatcreatedRECORD_ATTRIBUTESgetattrr dumps)rDrecorddataattrvalue __class__rrrgs    zJsonFormatter.format)rr_r`rirg __classcell__rrrprr'sr')NN)NNrrFFrA)__doc__r9r rZlogging.configZlogging.handlersrr"rrr8r@rr(r'rrrrs   ? K