o

$we��@s�
dZGd
d�de
�ZGdd�de�ZGdd�de�ZGdd�de�ZGd	d
�d
e�ZGdd�de�ZGd
d�de�ZGdd�de�Z	Gdd�de�Z
Gdd�de�ZGdd�de�ZGdd�de	�Z
Gdd�de	�ZGdd�de	�ZGdd�de	�ZGdd �d e	�ZGd!d"�d"e	�ZGd#d$�d$ee�ZGd%d&�d&e�ZGd'd(�d(e
�ZGd)d*�d*e	�ZGd+d,�d,e
�ZGd-d.�d.e�ZGd/d0�d0ee	�ZGd1d2�d2e	�ZGd3d4�d4e	�ZGd5d6�d6e	�ZGd7d8�d8e�ZGd9d:�d:e�ZGd;d<�d<e�Z Gd=d>�d>e�Z!d?S)@z*Core exceptions raised by the Redis clientc
@�eZ
dZd
S)�
RedisErrorN��__name__�
__module__�__qualname__�rr�I/home/arjun/projects/env/lib/python3.10/site-packages/redis/exceptions.pyr�
rc
@r
)�ConnectionErrorNrrrrrr
r	r
c
@r
)�TimeoutErrorNrrrrrrr	rc
@r
)�AuthenticationErrorNrrrrrrr	rc
@r
)�AuthorizationErrorNrrrrrr
r	r
c
@r
)�BusyLoadingErrorNrrrrrrr	rc
@r
)�InvalidResponseNrrrrrrr	rc
@r
)�
ResponseErrorNrrrrrr r	rc
@r
)�	DataErrorNrrrrrr$r	rc
@r
)�PubSubErrorNrrrrrr(r	rc
@r
)�
WatchErrorNrrrrrr,r	rc
@r
)�
NoScriptErrorNrrrrrr0r	rc
@�eZ
dZd
ZdS)�OutOfMemoryErroraU

    Indicates the database is full. Can only occur when either:
      * Redis maxmemory-policy=noeviction
      * Redis maxmemory-policy=volatile* and there are no evictable keys

    For more information see `Memory optimization in Redis <https://redis.io/docs/management/optimization/memory-optimization/#memory-allocation>`_. # noqa
    N�rrr�__doc__rrrrr4�
rc
@r
)�ExecAbortErrorNrrrrrr@r	rc
@r
)�
ReadOnlyErrorNrrrrrrDr	rc
@r
)�NoPermissionErrorNrrrrrrHr	rc
@r
)�ModuleErrorNrrrrrrLr	rc
@r)�	LockErrorz$Errors acquiring or releasing a lockNrrrrrrPs
rc
@r)�LockNotOwnedErrorzBError trying to extend or release a lock that is (no longer) ownedNrrrrrrW�

rc
@r)�ChildDeadlockedErrorzBError indicating that a child process is deadlocked after a fork()Nrrrrrr!\r r!c
@r)�$AuthenticationWrongNumberOfArgsErrorz^
    An error to indicate that the wrong number of args
    were sent to the AUTH command
    Nrrrrrr"a�
r"c
@r)�RedisClusterExceptionz4
    Base exception for the RedisCluster client
    Nrrrrrr$js
r$c
@r)�ClusterErrorzm
    Cluster errors occurred multiple times, resulting in an exhaustion of the
    command execution TTL
    Nrrrrrr%rr#r%c@�eZ
dZd
Zdd�ZdS)�ClusterDownErrora�

    Error indicated CLUSTERDOWN error received from cluster.
    By default Redis Cluster nodes stop accepting queries if they detect there
    is at least a hash slot uncovered (no available node is serving it).
    This way if the cluster is partially down (for example a range of hash
    slots are no longer covered) the entire cluster eventually becomes
    unavailable. It automatically returns available as soon as all the slots
    are covered again.
    cCs|
f
|_|
|_
dS�
N)�args�message)�self�resprrr�__init__�s


zClusterDownError.__init__N�rrrrr-rrrrr'{s

r'c@r&)�AskErrora)
    Error indicated ASK error received from cluster.
    When a slot is set as MIGRATING, the node will accept all queries that
    pertain to this hash slot, but only if the key in question exists,
    otherwise the query is forwarded using a -ASK redirection to the node that
    is target of the migration.

    src node: MIGRATING to dst node
        get > ASK error
        ask dst node > ASKING command
    dst node: IMPORTING from src node
        asking command only affects next command
        any op will be allowed after asking command
    cCsT|
f
|_|
|_
|
�d
�
\}}|�dd�\}}t|�
|_|t|�
f|_\|_|_dS)z#should only redirect to master node�
 �
:�
N)	r)r*�split�rsplit�int�slot_id�	node_addr�host�port)r+r,r6�new_noder8r9rrrr-�s





zAskError.__init__Nr.rrrrr/�s
r/c@r&)�
TryAgainErrorz�
    Error indicated TRYAGAIN error received from cluster.
    Operations on keys that don't exist or are - during resharding - split
    between the source and destination nodes, will generate a -TRYAGAIN error.
    c

OsdSr(r)r+r)�kwargsrrrr-�s
zTryAgainError.__init__Nr.rrrrr;�s
r;c
@seZ
dZd
ZdZdS)�ClusterCrossSlotErrorz�
    Error indicated CROSSSLOT error received from cluster.
    A CROSSSLOT error is generated when keys in a request don't hash to the
    same slot.
    z+Keys in request don't hash to the same slotN)rrrrr*rrrrr=�s
r=c
@r)�
MovedErrorz�
    Error indicated MOVED error received from cluster.
    A request sent to a node that doesn't serve this key will be replayed with
    a MOVED error that points to the correct node.
    Nrrrrrr>�s
r>c
@r)�MasterDownErrorz�
    Error indicated MASTERDOWN error received from cluster.
    Link with MASTER is down and replica-serve-stale-data is set to 'no'.
    Nrrrrrr?�r#r?c
@r)�SlotNotCoveredErrora

    This error only happens in the case where the connection pool will try to
    fetch what node that is covered by a given slot.

    If this error is raised the client should drop the current node layout and
    attempt to reconnect and refresh the node layout again
    Nrrrrrr@�rr@c
@r
)�MaxConnectionsErrorNrrrrrrA�r	rAN)"r�	Exceptionrr
rrr
rrrrrrrrrrrr�
ValueErrorrrr!r"r$r%r'r/r;r=r>r?r@rArrrr�<module>
s@