From: Zooko O'Whielacronx Date: Fri, 2 Jan 2009 20:27:09 +0000 (-0700) Subject: immutable: fix name change from BadOrMissingShareHash to BadOrMissingHash X-Git-Url: https://git.rkrishnan.org/%5B/frontends/index.php?a=commitdiff_plain;h=a52b5542e9008279fb801b8fb670d0e912cbec5e;p=tahoe-lafs%2Ftahoe-lafs.git immutable: fix name change from BadOrMissingShareHash to BadOrMissingHash One of the instances of the name accidentally didn't get changed, and pyflakes noticed. The new downloader/checker/verifier/repairer unit tests would also have noticed, but those tests haven't been rolled into a patch and applied to this repo yet... --- diff --git a/src/allmydata/immutable/download.py b/src/allmydata/immutable/download.py index fda9ef2a..daf9052c 100644 --- a/src/allmydata/immutable/download.py +++ b/src/allmydata/immutable/download.py @@ -27,7 +27,7 @@ class UnsupportedErasureCodec(BadURIExtension): pass class BadCrypttextHashValue(IntegrityCheckReject): pass -class BadOrMissingShareHash(IntegrityCheckReject): +class BadOrMissingHash(IntegrityCheckReject): pass class DownloadStopped(Exception): @@ -450,7 +450,7 @@ class ValidatedReadBucketProxy(log.PrefixingLogMixin): for i,h in enumerate(blockhashes): lines.append("%3d: %s" % (i, base32.b2a_or_none(h))) log.msg(" blockhashes:\n" + "\n".join(lines) + "\n") - raise BadOrMissingShareHash(le) + raise BadOrMissingHash(le) # If we made it here, the block is good. If the hash trees didn't # like what they saw, they would have raised a BadHashError, causing