S3: Fix check of uuid file stored in bucket, which was not working.
authorJoey Hess <joeyh@joeyh.name>
Mon, 13 Feb 2017 19:35:24 +0000 (15:35 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 13 Feb 2017 19:35:24 +0000 (15:35 -0400)
commit976676a7b09b327234780069fa7f9515c49972ef
treea9e012e2afe82f7278c1ea50825e220f69cf97ba
parentb6cfb9a73adcd14bf653e65e0314423a0d3bc346
S3: Fix check of uuid file stored in bucket, which was not working.

The check was broken in two ways.. First, nowhere did it error out when
checkUUIDFile found a different UUID already in the file. Instead,
it overwrote the uuid file.

And, checkUUIDFile's implementation was for some reason always failing with
a ConnectionClosed exception. Apparently something to do with using two
different runResourceT's and a response getting GCed inbetween. I'm pretty
sure that used to work, but changed to a more obviously correct
implementation.

This commit was sponsored by Peter Hogg on Patreon.
CHANGELOG
Remote/S3.hs