.SrSSKJr SSKJr SSKJr SSKJr SSKrSr\S-r\S -r \R(a\ r "S S \ 5r "S S \ 5r"SS\ 5r"SS\ 5r"SS\ 5r"SS\ 5r"SS\ 5r"SS\ 5rg)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*\rSrSrSrSrSrSrSrg)AbortException,zGException raised when a user aborts a command that needs to do cleanup.c:[RU5 XlgN) StandardError__init__reason)selfrs "platform/gsutil/gslib/exception.pyr AbortException.__init__/s4 Kc SUR-$NzAbortException: %srrs r__repr__AbortException.__repr__3 $++ --rc SUR-$rrrs r__str__AbortException.__str__6rrrN __name__ __module__ __qualname____firstlineno____doc__r rr__static_attributes__rrrr,sO..rrc.\rSrSrSrSSjrSrSrSrg) CommandException:abException 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). cF[RU5 XlX lg)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)rrr)s rr CommandException.__init__Cs4 K&rc[U5$r strrs rrCommandException.__repr__N t9rc SUR-$)NzCommandException: %srrs rrCommandException.__str__Qs !DKK //r)r)rN)Frr$rrr&r&:s '0rr&c\rSrSrSrSrg)ControlCExceptionUzException 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. r$Nrrr r!r"r#r$rrr3r3Us  rr3c\rSrSrSrSrg)GcloudStorageTranslationError^zEException raised when a gsutil command can't be translated to gcloud.r$Nr5r$rrr7r7^sMrr7c\rSrSrSrSrg)HashMismatchExceptioncz6Exception raised when data integrity validation fails.r$Nr5r$rrr:r:cs>rr:c*\rSrSrSrSrSrSrSrg)&IamChOnResourceWithConditionsExceptionhaRaised 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:[RX5 Xlgr  Exceptionr messagerrBs rr /IamChOnResourceWithConditionsException.__init__z t%Lrc[U5$r r,rs rr/IamChOnResourceWithConditionsException.__repr__~r/rc SUR-$)Nz*IamChOnResourceWithConditionsException: %srBrs rr.IamChOnResourceWithConditionsException.__str__s 7$,, FFrrINrr$rrr=r=hs"Grr=c*\rSrSrSrSrSrSrSrg)InvalidUrlErrorz%Exception raised when URL is invalid.c:[RX5 Xlgr r@rCs rr InvalidUrlError.__init__rErc[U5$r r,rs rrInvalidUrlError.__repr__r/rc SUR-$)NzInvalidUrlError: %srIrs rrInvalidUrlError.__str__s 4<< //rrINrr$rrrLrLs-0rrLc$\rSrSrSrSrSrSrg)ExternalBinaryErrorzCException raised when gsutil runs an external binary, and it fails.c:[RX5 Xlgr r@rCs rr ExternalBinaryError.__init__rErc SUR-$)NzExternalBinaryError: %srIrs rrExternalBinaryError.__repr__s $t|| 33rrIN)rrr r!r"r rr#r$rrrUrUsK4rrU)r" __future__rrrrsixNO_URLS_MATCHED_PREFIXNO_URLS_MATCHED_GENERICNO_URLS_MATCHED_TARGETPY3rAr rr&r3r7r:r=rLrUr$rrras, '%' *1GH/&877- .] .0}06 I I GYG: 0i 04)4r