Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

should retry on server-side errors #27

Closed
ericcj opened this issue Jul 10, 2012 · 2 comments · Fixed by #82
Closed

should retry on server-side errors #27

ericcj opened this issue Jul 10, 2012 · 2 comments · Fixed by #82
Labels
enhancement

Comments

@ericcj
Copy link
Contributor

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.
</body></html>

#<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
Copy link
Owner

adelevie commented Apr 8, 2013

Still a problem?

@ericcj
Copy link
Contributor Author

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 mentioned this issue Apr 22, 2013
Merged
@ericcj ericcj closed this as completed Apr 22, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

lots of fixes, read the commit messages ericcj/parse-ruby-client
2 participants
@ericcj @adelevie