sneak
5fd9d8e07b
check / check (push) Waiting to run
A missing blob during restore, a failed shallow verify and an invalid purge duration each printed their prefix twice. FetchBlob now returns the storage error as is, since restore and deep verify name the blob themselves; purge returns the duration parser's error unchanged; and a failed shallow verify returns only what failed, because the command prints "Verification failed:" before it. Deep verify words a storage error other than not found as a blob it could not check, and its log line no longer says S3. Already fixed for #314: the deep verify size message naming S3 and other errors called missing; tests now check both. Judgement call: the shallow verify error is a small error type, since the linter refuses an error built from a plain string. Not tested: the log line. Model: opus-5-5