rmoriz/digital_ocean — pull request #19 by petems (2013-12-16 16:50:07+00:00)
Title: Update ordering for Raising Status Errors

Found an edge case where an error would occur from Digitial Ocean, but it would not send a JSON response (normally because the API itself is down and nginx is sending an HTML page saying "502".

This leads to something like:

```
/opt/boxen/rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/json-1.8.1/lib/json/common.rb:155:in `parse': 757: unexpected token at ' (Faraday::Error::ParsingError)

```

etc.

I'll write up a test for this one, make a custom VCR cassette for it :+1: