Failed pull on clone unexpectedly leaves partial repo

[eschrock]

Expected Behavior

If you clone a repo, but the initial pull fails, you should be able to immediately re-try the clone with whatever error (creds, etc) fixed and have it succeed. We should clean up any partially created repository if later steps fail.

Actual Behavior

The first pull leaves behind the repo, so subsequent attempts fail:

titan clone s3://titan-data-demo/hello-world/postgres hello-world                  ✔  10068  09:52:12 
Exception in thread "main" io.titandata.client.infrastructure.ClientException: repository 'hello-world' already exists

Steps to Reproduce the Problem

Clone from a non-existent S3 bucket, observe that the repo still exists

Version

Titan 0.3.0