$dZddlmZddlmZddlmZddlmZddlZdZedzZed zZ ejre Z Gd d e Z Gd d e ZGdde ZGdde ZGdde ZGdde ZGdde ZGdde Zy)zagsutil exceptions. The exceptions in this module are for use across multiple different classes. )absolute_import)print_function)division)unicode_literalsNzNo URLs matchedz). Do the files you're operating on exist?z: %sc"eZdZdZdZdZdZy)AbortExceptionzGException raised when a user aborts a command that needs to do cleanup.c<tj|||_yN) StandardError__init__reason)selfr s "platform/gsutil/gslib/exception.pyr zAbortException.__init__/s4 DKc d|jzSNzAbortException: %sr rs r__repr__zAbortException.__repr__3 $++ --rc d|jzSrrrs r__str__zAbortException.__str__6rrN__name__ __module__ __qualname____doc__r rrrrrr,sO..rrc$eZdZdZddZdZdZy)CommandExceptionalException raised when a problem is encountered running a gsutil command. This exception should be used to signal user errors or system failures (like timeouts), not bugs (like an incorrect param value). For the latter you should raise Exception so we can see where/how it happened via gsutil -D (which will include a stack trace for raised Exceptions). cJtj|||_||_y)zInstantiate a CommandException. Args: reason: Text describing the problem. informational: Indicates reason should be printed as FYI, not a failure. N)r r r informational)rr r"s rr zCommandException.__init__Cs!4 DK&Drct|Sr strrs rrzCommandException.__repr__N t9rc d|jzS)NzCommandException: %srrs rrzCommandException.__str__Qs !DKK //rN)Frrrrr r :s '0rr ceZdZdZy)ControlCExceptionzException to report to analytics when the user exits via ctrl-C. This exception is never actually raised, but is used by analytics collection to provide a more descriptive name for user exit. Nrrrrrrrr)r)Us  rr)ceZdZdZy)GcloudStorageTranslationErrorzEException raised when a gsutil command can't be translated to gcloud.Nr*rrrr,r,^sMrr,ceZdZdZy)HashMismatchExceptionz6Exception raised when data integrity validation fails.Nr*rrrr.r.cs>rr.c"eZdZdZdZdZdZy)&IamChOnResourceWithConditionsExceptionaRaised when trying to use "iam ch" on an IAM policy with conditions. Because the syntax for conditions is fairly complex, it doesn't make sense to specify them on the command line using a colon-delimited set of values in the same way you'd specify simple bindings - it would be a complex and potentially surprising interface, which isn't what you want when dealing with permissions. Additionally, providing partial functionality -- e.g. if a policy contains bindings with conditions, still allow users to interact with bindings that don't contain conditions -- might sound tempting, but results in a bad user experience. Bindings can be thought of as a mapping from (role, condition) -> [members]. Thus, a user might think they're editing the binding for (role1, condition1), but they'd really be editing the binding for (role1, None). Thus, we just raise an error if we encounter a binding with conditions present, and encourage users to use "iam {get,set}" instead. c>tj||||_yr  Exceptionr messagerr4s rr z/IamChOnResourceWithConditionsException.__init__z tW%DLrct|Sr r$rs rrz/IamChOnResourceWithConditionsException.__repr__~r&rc d|jzS)Nz*IamChOnResourceWithConditionsException: %sr4rs rrz.IamChOnResourceWithConditionsException.__str__s 7$,, FFrNrrrrr0r0hs"Grr0c"eZdZdZdZdZdZy)InvalidUrlErrorz%Exception raised when URL is invalid.c>tj||||_yr r2r5s rr zInvalidUrlError.__init__r6rct|Sr r$rs rrzInvalidUrlError.__repr__r&rc d|jzS)NzInvalidUrlError: %sr9rs rrzInvalidUrlError.__str__s 4<< //rNrrrrr;r;s-0rr;ceZdZdZdZdZy)ExternalBinaryErrorzCException raised when gsutil runs an external binary, and it fails.c>tj||||_yr r2r5s rr zExternalBinaryError.__init__r6rc d|jzS)NzExternalBinaryError: %sr9rs rrzExternalBinaryError.__repr__s $t|| 33rN)rrrrr rrrrr@r@sK4rr@)r __future__rrrrsixNO_URLS_MATCHED_PREFIXNO_URLS_MATCHED_GENERICNO_URLS_MATCHED_TARGETPY3r3r rr r)r,r.r0r;r@rrrrIs, '%' *1GH/&877- .] .0}06 I I GYG: 0i 04)4r