Code Monkey home page Code Monkey logo

Comments (5)

keathley avatar keathley commented on August 11, 2024

There are a couple things that could be causing this. It shouldn't be possible to checkout a phantom before its started. A more likely solution is that its the phoenix server booting up / building assets. I'm not opposed to setting a longer timeout for httpoison though. Its probably better to return a more meaningful error from Wallaby anyway. Either way it would be worth digging into a bit to see exactly whats going on.

from wallaby.

aaronjensen avatar aaronjensen commented on August 11, 2024

We hit this too due to webpack building assets.

from wallaby.

keathley avatar keathley commented on August 11, 2024

Would you mind submitting a PR for this? I won't be able to get to it for a few days.

from wallaby.

steve0hh avatar steve0hh commented on August 11, 2024

I've had this error and made a fork of this project.

Basically i did the following:

  defp make_request(method, url, body) do
    headers = [{"Content-Type", "text/json"}]
    case HTTPoison.request(method, url, body, headers, [timeout: :infinity, recv_timeout: :infinity]) do
      {:ok, response} ->
        Poison.decode!(response.body)
      {:error, e} ->
        raise "There was an error calling: #{url} -> #{e.reason}"
    end
  end

Essential just setting both poison options : [timeout: :infinity, recv_timeout: :infinity].

It solves the timeout issue.

If you guys are ok, I could submit a PR.

from wallaby.

keathley avatar keathley commented on August 11, 2024

Please do.
On Mon, Aug 15, 2016 at 10:05 PM steve [email protected] wrote:

I've had this error and made a fork of this project.

Basically i did the following:

defp make_request(method, url, body) do
headers = [{"Content-Type", "text/json"}]
case HTTPoison.request(method, url, body, headers, [timeout: :infinity, recv_timeout: :infinity]) do
{:ok, response} ->
Poison.decode!(response.body)
{:error, e} ->
raise "There was an error calling: #{url} -> #{e.reason}"
end
end

Essential just setting both poison options : [timeout: :infinity,
recv_timeout: :infinity].

It solves the timeout issue.

If you guys are ok, I could submit a PR.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#74 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABkOb4ApgUidPpQfiu4DtC4-c1904yvMks5qgRrngaJpZM4JfRa0
.

from wallaby.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.