J,SSKJr SSKrSSKrSSKJrJrJrJrJrJ r SSK r SSK J r SSK Jr SSKJr SSKJr SSKJr SS KJr SS KJr \R6(a SS KJr SS KJr \R>r"S S\R@5r!g))absolute_importN)castAnyCallableOptionalSequenceUnion)AnonymousCredentials)service_account)types)futures)streaming_pull_manager)client) gapic_version) subscriber)SubscriberGrpcTransportc.^\rSrSrSrS\4U4Sjjr\S\S\SS4Sj5r \ r \ S\4Sj5r \ S\ 4S j5r\ U4S j5rSS \S \S /\4S\\R&\4S\SS\ S\ S\R.4SjjrSSjrSSjrSrSrU=r$)Client(adA subscriber client for Google Cloud Pub/Sub. This creates an object that is capable of subscribing to messages. Generally, you can instantiate this client with no arguments, and you get sensible defaults. Args: kwargs: Any additional arguments provided are sent as keyword keyword arguments to the underlying :class:`~google.cloud.pubsub_v1.gapic.subscriber_client.SubscriberClient`. Generally you should not need to set additional keyword arguments. Optionally, regional endpoints can be set via ``client_options`` that takes a single key-value pair that defines the endpoint. Example: .. code-block:: python from google.cloud import pubsub_v1 subscriber_client = pubsub_v1.SubscriberClient( # Optional client_options = { "api_endpoint": REGIONAL_ENDPOINT } ) kwargsc >[RRS5(a1S[RRS50US'[5US'[TU]"S0UD6 UR RUlSUl g)NPUBSUB_EMULATOR_HOST api_endpointclient_options credentialsF) osenvirongetr super__init__ _transport_host_target_closed)selfr __class__s ;lib/third_party/google/cloud/pubsub_v1/subscriber/client.pyr!Client.__init__Fsr ::>>0 1 1 /E F(F# $%9$:F= ! "6",,  filenamereturnc X[RRU5nX2S'U"S0UD6$)aSCreates an instance of this client using the provided credentials file. Args: filename: The path to the service account private key json file. kwargs: Additional arguments to pass to the constructor. Returns: A Subscriber :class:`~google.cloud.pubsub_v1.subscriber.client.Client` instance that is the constructed client. rr)r Credentialsfrom_service_account_file)clsr+rrs r(r/ Client.from_service_account_fileUs.&11KKHU +}}V}r*cUR$)zMReturn the target (where the API is). Returns: The location of the API. )r$r&s r(target Client.targetjs||r*cUR$)z_Return whether the client has been closed and cannot be used anymore. .. versionadded:: 2.8.0 )r%r3s r(closed Client.closedss ||r*cN>Sn[R"U[S9 [5$)aPThe underlying gapic API client. .. versionchanged:: 2.10.0 Instead of a GAPIC ``SubscriberClient`` client instance, this property is a proxy object to it with the same interface. .. deprecated:: 2.10.0 Use the GAPIC methods and properties on the client instance directly instead of through the :attr:`api` attribute. zThe "api" property only exists for backward compatibility, access its attributes directly thorugh the client instance (e.g. "client.foo" instead of "client.api.foo").)category)warningswarnDeprecationWarningr )r&msgr's r(api Client.api{s% ,  c$67wr* subscriptioncallbackzsubscriber.message.Message flow_control schedulerz$subscriber.scheduler.ThreadScheduleruse_legacy_flow_controlawait_callbacks_on_shutdownc [R"U6n[R"UUUUUUS9n[R "U5nUR X(RS9 U$)a8Asynchronously start receiving messages on a given subscription. This method starts a background thread to begin pulling messages from a Pub/Sub subscription and scheduling them to be processed using the provided ``callback``. The ``callback`` will be called with an individual :class:`google.cloud.pubsub_v1.subscriber.message.Message`. It is the responsibility of the callback to either call ``ack()`` or ``nack()`` on the message when it finished processing. If an exception occurs in the callback during processing, the exception is logged and the message is ``nack()`` ed. The ``flow_control`` argument can be used to control the rate of at which messages are pulled. The settings are relatively conservative by default to prevent "message hoarding" - a situation where the client pulls a large number of messages but can not process them fast enough leading it to "starve" other clients of messages. Increasing these settings may lead to faster throughput for messages that do not take a long time to process. The ``use_legacy_flow_control`` argument disables enforcing flow control settings at the Cloud Pub/Sub server, and only the client side flow control will be enforced. This method starts the receiver in the background and returns a *Future* representing its execution. Waiting on the future (calling ``result()``) will block forever or until a non-recoverable error is encountered (such as loss of network connectivity). Cancelling the future will signal the process to shutdown gracefully and exit. .. note:: This uses Pub/Sub's *streaming pull* feature. This feature properties that may be surprising. Please take a look at https://cloud.google.com/pubsub/docs/pull#streamingpull for more details on how streaming pull behaves compared to the synchronous pull method. Example: .. code-block:: python from google.cloud import pubsub_v1 subscriber_client = pubsub_v1.SubscriberClient() # existing subscription subscription = subscriber_client.subscription_path( 'my-project-id', 'my-subscription') def callback(message): print(message) message.ack() future = subscriber_client.subscribe( subscription, callback) try: future.result() except KeyboardInterrupt: future.cancel() # Trigger the shutdown. future.result() # Block until the shutdown is complete. Args: subscription: The name of the subscription. The subscription should have already been created (for example, by using :meth:`create_subscription`). callback: The callback function. This function receives the message as its only argument and will be called from a different thread/ process depending on the scheduling strategy. flow_control: The flow control settings. Use this to prevent situations where you are inundated with too many messages at once. scheduler: An optional *scheduler* to use when executing the callback. This controls how callbacks are executed concurrently. This object must not be shared across multiple ``SubscriberClient`` instances. use_legacy_flow_control (bool): If set to ``True``, flow control at the Cloud Pub/Sub server is disabled, though client-side flow control is still enabled. If set to ``False`` (default), both server-side and client-side flow control are enabled. await_callbacks_on_shutdown: If ``True``, after canceling the returned future, the latter's ``result()`` method will block until the background stream and its helper threads have been terminated, and all currently executing message callbacks are done processing. If ``False`` (default), the returned future's ``result()`` method will not block after canceling the future. The method will instead return immediately after the background stream and its helper threads have been terminated, but some of the message callback threads might still be running at that point. Returns: A future instance that can be used to manage the background stream. )rCrDrErF)rBon_callback_error)r FlowControlrStreamingPullManagerr StreamingPullFutureopen set_exception) r&rArBrCrDrErFmanagerfutures r( subscribeClient.subscribesbR((,7 (==  %$;(C  ,,W5 h:N:N O r*cr[SUR5nURR5 SUlg)zClose the underlying channel to release socket resources. After a channel has been closed, the client instance cannot be used anymore. This method is idempotent. rTN)rr" grpc_channelcloser%)r& transports r(rT Client.close s.2DOOD $$& r*c>UR(a [S5eU$)Nz4Closed subscriber cannot be used as context manager.)r% RuntimeErrorr3s r( __enter__Client.__enter__s <<UV V r*c$UR5 g)N)rT)r&exc_typeexc_valexc_tbs r(__exit__Client.__exit__s  r*)r%r$)rNFF)r,N)r,r)__name__ __module__ __qualname____firstlineno____doc__rr! classmethodstrr/from_service_account_jsonpropertyr4boolr7r?rr r rIrrr rKrPrTrYr___static_attributes__ __classcell__)r's@r(rr(s.:  &) $!: .<>FJ(-,1xx893>?xE--x78 x BC x "& x&*x  $ $xt  r*r)" __future__rrtypingrrrrrr r;google.auth.credentialsr google.oauth2r google.cloud.pubsub_v1r !google.cloud.pubsub_v1.subscriberr +google.cloud.pubsub_v1.subscriber._protocolr$google.pubsub_v1.services.subscriberrsubscriber_clientgoogle.pubsub_v1rpackage_version TYPE_CHECKINGr4google.pubsub_v1.services.subscriber.transports.grpcr __version__SubscriberClientrrr*r(r|sa' AA8)(5NL= 1)) s  / /sr*