You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using this library and when the IPInfo API returns a 503 response, the handler for IPInfo raises an error because the return from the API is not a JSON, but rather a String which states the following,
unexpected token at 'upstream connect error or disconnect/reset before headers. reset reason: connection timeout' (JSON::ParserError)
I have looked at the code and it seems the ipinfo-rails gem relies on the ipinfo Ruby gem version 1.0.1. But the latest version of the IPInfo ruby gem is 2.2.1.
Any idea why we're keeping the Ruby gem's dependency so low?
Thanks for your answer.
The text was updated successfully, but these errors were encountered:
We're using this library and when the IPInfo API returns a 503 response, the handler for IPInfo raises an error because the return from the API is not a JSON, but rather a String which states the following,
I have looked at the code and it seems the ipinfo-rails gem relies on the ipinfo Ruby gem version 1.0.1. But the latest version of the IPInfo ruby gem is 2.2.1.
Any idea why we're keeping the Ruby gem's dependency so low?
Thanks for your answer.
The text was updated successfully, but these errors were encountered: