Closed NovaRemitly closed 8 years ago
So it looks like that bad_json
message was coming from B2 itself. Also strange is that the integration tests (which do pass, at least when I test them) successfully use a bucket name with several dashes in them. Also, git-annex-remote-b2
shouldn't try to create a bucket unless the list buckets API were returning invalid data.
Does this still happen? I suspect it was a temporary API bug on Backblaze's part.
Closing for idleness; if you still see this, please reopen/comment.
I tried to use b2 with a bucket name like
my-cool-bucket
. I got the following error:Problems with this error message:
I tried deleting the bucket and letting git annex create it, but that produced the same error message.
I had some other parameters set that might be affecting this:
encryption=pubkey mac=HMACSHA512
and my Backblaze credentials were set in shell environment variables.Changing the name to MyCoolBucket worked fine.