File: //lib64/python3.9/site-packages/borg/__pycache__/logger.cpython-39.opt-1.pyc
a
HZ�h�# � @ s| d Z ddlZddlZddlZddlZddlZddlZddlZdaddd�Z ddd �Z
d
d � Z dd d
�Z G dd� dej
�ZdS )a logging 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
<https://docs.python.org/3/howto/logging.html#when-to-use-logging>`_
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
� NFc C s2 |� d|� d|j � d| � �}tt �}|�|� d S )N�:z: )�__name__�
create_logger�warning)�message�category�filename�lineno�file�line�msg�logger� r �1/usr/lib64/python3.9/site-packages/borg/logger.py� _log_warning/ s r �BORG_LOGGING_CONF�infoc
C s� d}|rt j�||�}|r�z|t j�|�}t|�� }tj�|� W d � n1 sR0 Y da t�
t �}t�
d�} || _ |�
d|� d�� tt_W dS ty� }
zt|
�}W Y d}
~
n
d}
~
0 0 t�
d�}t�| �} |r�|s�d} nd} |r�t| �nt�| �}
| �|
� t�
d�} |
| _|| _ t �rF|j�rF|jd �� |j�� |�| � |� |� � � da t�
t �}|�r�|� d
|� d |� d �� |�
d
� tt_| S )a� setup 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.
NTZborgz'using logging configuration read from "�"� z/$LOG %(levelname)s %(name)s Remote: %(message)sz %(message)sr zsetup_logging for "z" failed with "z".z,using builtin fallback logging configuration) �os�environ�get�path�abspath�open�loggingZconfigZ
fileConfig�
configured� getLoggerr �json�debugr �warnings� showwarning� Exception�strZ
StreamHandler�
JsonFormatter� FormatterZ setFormatter� formatter�handlers�close�clearZ
addHandler�setLevel�upperr )�streamZ
conf_fnameZenv_var�levelZis_server �err_msg�fr
Z borg_logger�errZhandler�fmtr& r r r �
setup_logging8 sN
*
r2 c C s\ z@t �� j} t �| �}|du s(|jtkr:| j} t �| �}q|jW S tyV t Y S 0 dS )z�find the name of the first module calling this module
if we cannot find it, we return the current module's name
(__name__) instead.
N)�inspectZ currentframe�f_backZ getmoduler �AttributeError)�frame�moduler r r �find_parent_modulew s
r8 c s G � fdd�d�� � | �S )a� lazily 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.
c sn e Zd Zddd�Zedd� �Z� fdd�Zdd � Zd
d � Zd d
� Z dd� Z
dd� Z dd� Z dd� Z
dd� ZdS )z!create_logger.<locals>.LazyLoggerNc S s |pt � | _d | _d S �N)r8 �_LazyLogger__name�_LazyLogger__real_logger)�self�namer r r �__init__� s z*create_logger.<locals>.LazyLogger.__init__c S sP | j d u rJtstd��t�| j�| _ | j�d�rJ| j jtjkrJ| j � d� | j S )Nz8tried to call a logger before setup_logging() was calledz borg.debug.ZWARNING)
r; r r" r r r: �
startswithr- ZNOTSETr* )r< r r r Z__logger� s
z*create_logger.<locals>.LazyLogger.__loggerc s � | j d | �S )N�.)r: )r< �suffix��
LazyLoggerr r �getChild� s z*create_logger.<locals>.LazyLogger.getChildc _ s | j j|i |��S r9 )�_LazyLogger__loggerr* �r< �args�kwr r r r* � s z*create_logger.<locals>.LazyLogger.setLevelc _ s0 d|v r |� d�|�di �d< | jj|i |��S �N�msgidZextra)�pop�
setdefaultrE �logrF r r r rM � s z%create_logger.<locals>.LazyLogger.logc _ s0 d|v r |� d�|�di �d< | jj|i |��S rI )rK rL rE � exceptionrF r r r rN � s z+create_logger.<locals>.LazyLogger.exceptionc _ s0 d|v r |� d�|�di �d< | jj|i |��S rI )rK rL rE r rF r r r r � s z'create_logger.<locals>.LazyLogger.debugc _ s0 d|v r |� d�|�di �d< | jj|i |��S rI )rK rL rE r rF r r r r � s z&create_logger.<locals>.LazyLogger.infoc _ s0 d|v r |� d�|�di �d< | jj|i |��S rI )rK rL rE r rF r r r r � s z)create_logger.<locals>.LazyLogger.warningc _ s0 d|v r |� d�|�di �d< | jj|i |��S rI )rK rL rE �errorrF r r r rO � s z'create_logger.<locals>.LazyLogger.errorc _ s0 d|v r |� d�|�di �d< | jj|i |��S rI )rK rL rE �criticalrF r r r rP � s z*create_logger.<locals>.LazyLogger.critical)N)r �
__module__� __qualname__r> �propertyrE rD r* rM rN r r r rO rP r rB r r rC � s
rC r )r= r rB r r � s 8r c s e Zd ZdZ� fdd�Z� ZS )r$ )� levelnamer= r rJ c sJ t � �|� d|jddd�}| jD ] }t||d �}|r"|||< q"t�|�S )NZ log_messager ZCRITICAL)�type�timer rT )�super�formatZcreated�RECORD_ATTRIBUTES�getattrr �dumps)r< �record�data�attr�value�� __class__r r rX � s �
zJsonFormatter.format)r rQ rR rY rX �
__classcell__r r r` r r$ � s r$ )NN)NNr r FF)N)�__doc__r3 r r Zlogging.configZlogging.handlersr r r r r2 r8 r r% r$ r r r r �<module> s
?
K