Yf"dZddlZddlZddlmZddlmZddlmZddl m Z ddl m Z dd l mZmZmZmZmZmZdd lmZd Zejd Zd ZGddeZGdde ZdS)zAMQP Channels.N) defaultdict)Queue)ensure_promise)spec)AbstractChannel) ChannelErrorConsumerCancelled MessageNackedRecoverableChannelErrorRecoverableConnectionErrorerror_for_code)queue_declare_ok_t)ChannelamqpzuRejecting message with delivery tag %r for reason of having no callbacks. consumer_tag=%r exchange=%r routing_key=%r.ceZdZdS)VDeprecationWarningN)__name__ __module__ __qualname__>/var/www/html/env/lib/python3.11/site-packages/amqp/channel.pyrrsDrrc eZdZdZejejjdejejjejejj dejejj dejejj ejej j ejej jejej jejej jejejjejejjejejj dejejjdejejjdejejjdejejjdejejjdejejjdd ejejjdejejjd d ejejjejejjejejjd d ejejjejejjejejj ejej!j ejejj"d ejejj#d hZ$d e$DZ$ejjejjfZ% dKfd Z&dLdZ'dZ(dZ)dZ* dMdZ+dZ,dZ-dZ.dZ/dZ0dZ1dZ2 dNd!Z3 dOd#Z4 dPd%Z5 dPd&Z6 dPd'Z7 dQd)Z8 dRd+Z9 dSd-Z:dTd/Z;dUd0Zd4Z?d5Z@ dWd7ZAd8ZBdTd9ZCdLd:ZDd;ZE dXd=ZFeFZGd>ZH dYd@ZIdZdAZJdZdBZKd[dCZLdDZMdEZNdFZOdGZPdZdHZQdIZRdJZSxZTS)\raAMQP Channel. The channel class provides methods for a client to establish a virtual connection - a channel - to a server and for both peers to operate the virtual connection thereafter. GRAMMAR:: channel = open-channel *use-channel close-channel open-channel = C:OPEN S:OPEN-OK use-channel = C:FLOW S:FLOW-OK / S:FLOW C:FLOW-OK / functional-class close-channel = C:CLOSE S:CLOSE-OK / S:CLOSE C:CLOSE-OK Create a channel bound to a connection and using the specified numeric channel_id, and open on the server. The 'auto_decode' parameter (defaults to True), indicates whether the library should attempt to decode the body of Messages to a Unicode string if there's a 'content_encoding' property for the message. If there's no 'content_encoding' property, or the decode raises an Exception, the message body is left as plain bytes. BsBBbslllssLbssT)contentLbsslBsssLbci|] }|j| Sr) method_sig).0ms r zChannel.[s222A a222rNc|r||n|}td|t ||d|_d|_t|_ i|_ i|_ ||_ tt|_t|_t#||_d|_|jjr |j|_d}dS)Nzusing channel_id: %sFT) is_openactivereturned_messages callbackscancel_callbackseventsno_ack_consumerson_open_confirm_selected)_claim_channel_id_get_free_channel_id AMQP_LOGGERdebugsuper__init__r+r,rr-r.r/ auto_decodersetr0r1rr2r3 connectionconfirm_publishbasic_publish_confirm basic_publish)selfr< channel_idr:r2 __slots__ __class__s rr9zChannel.__init__as  ;  ( ( 4 4 4 4#88::J0*=== Z000  !& "&!#&& #%g.. "' ? * tt ||||||dYdSwxYw)N)rr redeliveredrrT)requeue)channel delivery_infor.KeyErrorr6warning!REJECTED_MESSAGE_WITHOUT_CALLBACK basic_reject)r@rrrrrmsgfuns rrZzChannel._on_basic_deliverIs ((& &    ..C CHHHHH : : :   1lHk      lD  9 9 9 9 9 9  :s 0AA87A8c|tjj|d||ftjjtjjgd}|rt |dkr |j|S|j|S)aDirect access to a queue. This method provides a direct access to the messages in a queue using a synchronous dialogue that is designed for specific types of application where synchronous functionality is more important than performance. PARAMETERS: queue: shortstr Specifies the name of the queue to consume from. If the queue name is null, refers to the current queue for the channel, which is the last declared queue. RULE: If the client did not previously declare a queue, and the queue name in this method is empty, the server MUST raise a connection exception with reply code 530 (not allowed). no_ack: boolean no acknowledgment needed If this field is set the server does not expect acknowledgments for messages. That is, when a message is delivered to the client the server automatically and silently acknowledges it on behalf of the client. This functionality increases performance but at the cost of reliability. Messages can get lost if a client dies before it can deliver them to the application. Non-blocking, returns a amqp.basic_message.Message object, or None if queue is empty. rTr) rurrTGetGetOkGetEmptylen _on_get_empty _on_get_ok)r@rrrxrets r basic_getzChannel.basic_get_s|J JNFQv$6*"DJ$78   ,c#hhll%4%s+ +t$$rcdSrEr)r@ cluster_ids rrzChannel._on_get_emptys rc.||_|||||d|_|S)N)rrrr message_count)rr)r@rrrrrrs rrzChannel._on_get_oks. (& &*    rBssbbc |jstd|jjdi} | ddr2 |jdn#t j$rYnwxYw |jj|5| tj j |d||||f|cdddS#1swxYwYdS#t j$rtdwxYw) a Publish a message. This method publishes a message to a specific exchange. The message will be routed to queues as defined by the exchange configuration and distributed to any active consumers when the transaction, if any, is committed. When channel is in confirm mode (when Connection parameter confirm_publish is set to True), each message is confirmed. When broker rejects published message (e.g. due internal broker constrains), MessageNacked exception is raised and set confirm_timeout to wait maximum confirm_timeout second for message to confirm. PARAMETERS: exchange: shortstr Specifies the name of the exchange to publish to. The exchange name can be empty, meaning the default exchange. If the exchange name is specified, and that exchange does not exist, the server will raise a channel exception. RULE: The server MUST accept a blank exchange name to mean the default exchange. RULE: The exchange MAY refuse basic content in which case it MUST raise a channel exception with reply code 540 (not implemented). routing_key: shortstr Message routing key Specifies the routing key for the message. The routing key is used for routing messages depending on the exchange configuration. mandatory: boolean indicate mandatory routing This flag tells the server how to react if the message cannot be routed to a queue. If this flag is True, the server will return an unroutable message with a Return method. If this flag is False, the server silently drops the message. RULE: The server SHOULD implement the mandatory flag. immediate: boolean request immediate delivery This flag tells the server how to react if the message cannot be routed to a queue consumer immediately. If this flag is set, the server will return an undeliverable message with a Return method. If this flag is zero, the server will queue the message, but with no guarantee that it will ever be consumed. RULE: The server SHOULD implement the immediate flag. timeout: short timeout for publish Set timeout to wait maximum timeout second for message to publish. confirm_timeout: short confirm_timeout for publish in confirm mode When the channel is in confirm mode set confirm_timeout to wait maximum confirm_timeout second for message to confirm. z basic_publish: connection closed capabilitieszconnection.blockedFr)timeoutNzbasic_publish: timed out)r<r client_propertiesget drain_eventssocketr transporthaving_timeoutrurrTPublishr ) r@rrr mandatory immediaterconfirm_timeoutrxrs r_basic_publishzChannel._basic_publishsv 4,244 4 cc."55    0% 8 8  ,,Q,7777>     F*99'BB  ''J&+y)Dc                   ~ F F F)*DEE E FsBA**A<;A<C%,C C%CC%C C%%Dc6|dd}d}|jsd|_||j|i|}|p|dd}|t jjt jj g|||S)NrcL|tjjkrtdSrE)rrTr_r )methodargss rconfirm_handlerz6Channel.basic_publish_confirm..confirm_handlers#((#oo%)(rTr)rr) rer3confirm_selectrrrsrrTr]r_)r@rkwargsrrrrs rr>zChannel.basic_publish_confirms **%6== & & & % "%)D "    ! ! !!d!42622!@VZZ 4%@%@ 4:>4:?3*!  # # # rlBbcv|tjj||||ftjjS)a Specify quality of service. This method requests a specific quality of service. The QoS can be specified for the current channel or for all channels on the connection. The particular properties and semantics of a qos method always depend on the content class semantics. Though the qos method could in principle apply to both peers, it is currently meaningful only for the server. PARAMETERS: prefetch_size: long prefetch window in octets The client can request that messages be sent in advance so that when the client finishes processing a message, the following message is already held locally, rather than needing to be sent down the channel. Prefetching gives a performance improvement. This field specifies the prefetch window size in octets. The server will send a message in advance if it is equal to or smaller in size than the available prefetch size (and also falls into other prefetch limits). May be set to zero, meaning "no specific limit", although other prefetch limits may still apply. The prefetch-size is ignored if the no-ack option is set. RULE: The server MUST ignore this setting when the client is not processing any messages - i.e. the prefetch size does not limit the transfer of single messages to a client, only the sending in advance of more messages while the client still has one or more unacknowledged messages. prefetch_count: short prefetch window in messages Specifies a prefetch window in terms of whole messages. This field may be used in combination with the prefetch-size field; a message will only be sent in advance if both prefetch windows (and those at the channel and connection level) allow it. The prefetch- count is ignored if the no-ack option is set. RULE: The server MAY send less data in advance than allowed by the client's specified prefetch windows but it MUST NOT send more. a_global: boolean Defines a scope of QoS. Semantics of this parameter differs between AMQP 0-9-1 standard and RabbitMQ broker: MEANING IN AMQP 0-9-1: False: shared across all consumers on the channel True: shared across all consumers on the connection MEANING IN RABBITMQ: False: applied separately to each new consumer on the channel True: shared across all consumers on the channel rr)rurrTQosQosOk)r@ prefetch_sizeprefetch_counta_globalrxs r basic_qoszChannel.basic_qos!s<J JNF]NH$M!    rcP|tjjd|fS)a{Redeliver unacknowledged messages. This method asks the broker to redeliver all unacknowledged messages on a specified channel. Zero or more messages may be redelivered. This method is only allowed on non-transacted channels. RULE: The server MUST set the redelivered flag on all messages that are resent. RULE: The server MUST raise a channel exception if this is called on a transacted channel. PARAMETERS: requeue: boolean requeue the message If this field is False, the message will be redelivered to the original recipient. If this field is True, the server will attempt to requeue the message, potentially then delivering it to an alternative subscriber. r)rurrTRecoverr@rs r basic_recoverzChannel.basic_recoverks#: 2C'DDDrcP|tjjd|fS)Nr)rurrT RecoverAsyncrs rbasic_recover_asynczChannel.basic_recover_asyncs! 7wjIIIrcR|tjj|||fS)a& Reject an incoming message. This method allows a client to reject a message. It can be used to interrupt and cancel large incoming messages, or return untreatable messages to their original queue. RULE: The server SHOULD be capable of accepting and process the Reject method while sending message content with a Deliver or Get-Ok method. I.e. the server should read and process incoming methods while sending output frames. To cancel a partially-send content, the server sends a content body frame of size 1 (i.e. with no data except the frame-end octet). RULE: The server SHOULD interpret this method as meaning that the client is unable to process the message at this time. RULE: A client MUST NOT use this method as a means of selecting messages to process. A rejected message MAY be discarded or dead-lettered, not necessarily passed to another client. PARAMETERS: delivery_tag: longlong server-assigned delivery tag The server-assigned and channel-specific delivery tag RULE: The delivery tag is valid only within the channel from which the message was received. I.e. a client MUST NOT receive a message on one channel and then acknowledge it on another. RULE: The server MUST NOT use a zero value for delivery tags. Zero is reserved for client use, meaning "all messages so far received". requeue: boolean requeue the message If this field is False, the message will be discarded. If this field is True, the server will attempt to requeue the message. RULE: The server MUST NOT deliver the message to the same client within the context of the current channel. The recommended strategy is to attempt to deliver the message to an alternative consumer, and if that is not possible, to move the message to a dead-letter queue. The server MAY use more sophisticated tracking to hold the message on the queue and redeliver it to the same client at a later stage. )rurrTReject)r@rrrxs rrzChannel.basic_rejects.J J v g'>   rct||tjjt}|jd}|s||D]}|||||dS)aReturn a failed message. This method returns an undeliverable message that was published with the "immediate" flag set, or an unroutable message published with the "mandatory" flag set. The reply code and text provide information about the reason that the message was undeliverable. PARAMETERS: reply_code: short The reply code. The AMQ reply codes are defined in AMQ RFC 011. reply_text: shortstr The localised reply text. This text can be logged as an aid to resolving issues. exchange: shortstr Specifies the name of the exchange that the message was originally published to. routing_key: shortstr Message routing key Specifies the routing key name specified when the message was published. basic_returnN)rrrTr[r r0r) r@rvrwrrmessageexchandlersrs rr\zChannel._on_basic_returnsvB  DJ$5|  ;??>22 I  : :H HS(K 9 9 9 9 : :rcl|tjjtjjS)zCommit the current transaction. This method commits all messages published and acknowledged in the current transaction. A new transaction starts immediately after a commit. rr)rurTxCommitCommitOkras r tx_commitzChannel.tx_commit&TW5EFFFrcl|tjjtjjS)zAbandon the current transaction. This method abandons all messages published and acknowledged in the current transaction. A new transaction starts immediately after a rollback. rr)rurrRollback RollbackOkras r tx_rollbackzChannel.tx_rollback%s' 0tw7IJJJrcl|tjjtjjS)zSelect standard transaction mode. This method sets the channel to use standard transactions. The client must use this method at least once on a channel before using the Commit or Rollback methods. rr)rurrSelectSelectOkras r tx_selectzChannel.tx_select.r"rcz|tjjd|f|rdntjjS)aEnable publisher confirms for this channel. Note: This is an RabbitMQ extension. Can now be used if the channel is in transactional mode. :param nowait: If set, the server will not respond to the method. The client should not wait for a reply method. If the server could not complete the method it will raise a channel or connection exception. rNrr)rurConfirmr(r))r@rs rrzChannel.confirm_select7s@ L vi:T\%:    rc>|jdD]}|||dS)Nrr0r@rrrs rr^zChannel._on_basic_ackIs7 K0 - -H H\8 , , , , - -rc>|jdD]}|||dS)N basic_nackr.r/s rr`zChannel._on_basic_nackMs7 L1 - -H H\8 , , , , - -r)NTNrE)rrnror)FFTFNr)FFr)rnrnFNr)rnFNr)rnFFFTFNr)rnFFFr)rnFr)Fr$)Fr) rnrnFFFFNNNr)rnrnFFNNr)r)F)r$)Urrr__doc__rrrrLrNrPrrRrrrrrrrrTrUrWrrYrrr  RecoverOkr[rr r%r)r,r]r__METHODS_ALLOWED_METHODS_WHEN_CLOSINGr9rFrbrjrmryrMrOrrQrrlrSrrrrrrrrrrrrVrXrrrZrrrrr?r>rrrrr\r!r&r*rr^r` __classcell__)rCs@rrr s8  DL&// DL()) DL%s++ DL'-- DL'(( DM+,, DM*++ DM()) DM*++ DJ%&& DJ'(( DJ(%00 DJ'-- DJ&,, DJ%s++ DJ'-- DJ(#.. DJ&>>> DJ'-- DJ$gt<<< DJ$%% DJ()) DJ%vt<<< DG$%% DG&'' DG$%% DL)** DJND)) DJOT**;H>32222H DL0%! =A& & & & & & P7777    &&&*=C?#?#?#?#B333j   / / / b.%.%.%`EEE"   4***bGLCG +@ @ @ @ DAF%. . . . `AC;CL L L L \CE=E7 7 7 7 f:<8@g g g g R9;:A7 7 7 7 r>C@E-7bbbbH"$=B#I I I I V: : : : p0 0 0 0 d,,,,\ E E E'''===AFAE'+%oFoFoFoFb#M(H H H H TEEEE>JJJJG G G G R(:(:(:LGGGKKKGGG    $----------rr)r2loggingr collectionsrrrvinerrnrabstract_channelr exceptionsr r r r r rprotocolr__all__ getLoggerr6rDeprecationWarningrrrrrr@se ######------)))))))))))))))))((((( g'' %!      ,   o -o -o -o -o -oo -o -o -o -o -r