+hdZGddeZGddeZGddeZGddeZGd d eZGd d eZGd deZGddeZ GddeZ GddeZ GddeZ Gdde Z Gdde ZGdde ZGdde ZGdd e ZGd!d"e ZGd#d$eeZGd%d&eZGd'd(eZGd)d*e ZGd+d,eZGd-d.eZGd/d0ee ZGd1d2e ZGd3d4e ZGd5d6e ZGd7d8eZGd9d:eZGd;deZ!y?)@z*Core exceptions raised by the Redis clientc eZdZy) RedisErrorN__name__ __module__ __qualname__C/var/www/html/venv/lib/python3.12/site-packages/redis/exceptions.pyrrr rc eZdZy)ConnectionErrorNrrr r r r r r r c eZdZy) TimeoutErrorNrrr r rr r r rc eZdZy)AuthenticationErrorNrrr r rrr r rc eZdZy)AuthorizationErrorNrrr r rrr r rc eZdZy)BusyLoadingErrorNrrr r rrr r rc eZdZy)InvalidResponseNrrr r rrr r rc eZdZy) ResponseErrorNrrr r rr r r rc eZdZy) DataErrorNrrr r rr$r r rc eZdZy) PubSubErrorNrrr r rr(r r rc eZdZy) WatchErrorNrrr r rr,r r rc eZdZy) NoScriptErrorNrrr r r!r!0r r r!ceZdZdZy)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 `_. # noqa Nrrr__doc__rr r r#r#4  r r#c eZdZy)ExecAbortErrorNrrr r r(r(@r r r(c eZdZy) ReadOnlyErrorNrrr r r*r*Dr r r*c eZdZy)NoPermissionErrorNrrr r r,r,Hr r r,c eZdZy) ModuleErrorNrrr r r.r.Lr r r.ceZdZdZy) LockErrorz$Errors acquiring or releasing a lockNr$rr r r0r0Ps * r r0ceZdZdZy)LockNotOwnedErrorzBError trying to extend or release a lock that is (no longer) ownedNr$rr r r2r2WHr r2ceZdZdZy)ChildDeadlockedErrorzBError indicating that a child process is deadlocked after a fork()Nr$rr r r5r5\r3r r5ceZdZdZy)$AuthenticationWrongNumberOfArgsErrorz^ An error to indicate that the wrong number of args were sent to the AUTH command Nr$rr r r7r7a   r r7ceZdZdZy)RedisClusterExceptionz4 Base exception for the RedisCluster client Nr$rr r r:r:js  r r:ceZdZdZy) ClusterErrorzm Cluster errors occurred multiple times, resulting in an exhaustion of the command execution TTL Nr$rr r r<r<rr8r r<ceZdZdZdZy)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. c"|f|_||_yN)argsmessage)selfresps r __init__zClusterDownError.__init__sG  r Nrrrr%rErr r r>r>{s r r>ceZdZdZdZy)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 c|f|_||_|jd\}}|jdd\}}t ||_|t |fx|_\|_|_y)z#should only redirect to master node :N) rArBsplitrsplitintslot_id node_addrhostport)rCrDrPnew_noderRrSs r rEzAskError.__init__s`G   JJsO__S!, d7| 04c$i?-DIr NrFrr r rHrHs  @r rHceZdZdZdZy) 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. cyr@r)rCrAkwargss r rEzTryAgainError.__init__s r NrFrr r rVrVs   r rVceZdZdZdZy)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)rrrr%rBrr r rZrZs rHrVrZr\r^r`rbrr r res,   j  :  /      j  J    *    M   }   ]  M    -  J    9  =  I  :  |]  @}@4 M