should retry on server-side errors #27

ericcj opened this Issue Jul 10, 2012 · 2 comments


None yet

2 participants

ericcj commented Jul 10, 2012
#<JSON::ParserError: 757: unexpected token at '<html><body><h1>502 Bad Gateway</h1>

#<JSON::ParserError: 757: unexpected token at '<html><body><h1>503 Service Unavailable</h1>
No server is available to handle this request.

#<JSON::ParserError: A JSON text must at least contain two octets!>
gems/ruby-1.9.3-p194/gems/json-1.7.3/lib/json/common.rb:155:in `initialize' -- ge
ms/ruby-1.9.3-p194/gems/json-1.7.3/lib/json/common.rb:155:in `new' -- gems/ruby-1.9.3-p194/gems/json-1
.7.3/lib/json/common.rb:155:in `parse' -- gems/ruby-1.9.3-p194/gems/parse-ruby-client-0.1.2.ericcj.1/l
ib/parse/client.rb:58:in `request' -- gems/ruby-1.9.3-p194/gems/parse-ruby-client-0.1.2.ericcj.1/lib/p
arse/query.rb:82:in `get'
adelevie commented Apr 8, 2013

Still a problem?

ericcj commented Apr 10, 2013

yes. it's unfortunate that the parse api returns html errors but this happens frequently and we should treat it as a transient error that can be retried

@ericcj ericcj closed this Apr 22, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment