BigTest has a proxy error with gatsby

[jbolda]

It appears that Gatsby (run through netlify dev) starts up slowly enough and maybe doesn't provide the correct signals that it is ready, and BigTest times out the connection with a proxy error. See this clip from stream.

Proxy error: Error: connect ECONNREFUSED 127.0.0.1:3000

[cowboyd]

As you can see, the app server inside bigtest itself will just keep looping until it receives a response.ok

https://github.com/thefrontside/bigtest/blob/effection-v2/packages/server/src/app-server.ts#L36-L56

You can increase the amount of time that it will wait from the bigtest ci

If netlify is returning response.ok when in fact, it is not ok, then we might have to add an extension point where you can insert custom code into the health check to determine if the response is "actually ok"

GitHub

bigtest/app-server.ts at effection-v2 · thefrontside/bigtest

Ensure your React/Vue/Ember/anything app works perfectly across browsers. - bigtest/app-server.ts at effection-v2 · thefrontside/bigtest

[jbolda]

Ah yea, that makes sense. I was looking at the CLI options too and didn't think to look into that. I guess I assumed it was just waiting until it started.

Notes for checking if this is the issue / documenting it:

• the CLI option: https://github.com/thefrontside/bigtest/blob/effection-v2/packages/cli/src/cli.ts#L97
• document the CLI option and how it starts up
• throw an error pointing to the timeout option if it does fail with timeout
• serve page that notes the error state, what happened, and about the timeout? (looks like it crashes so we might not be able to do this)

GitHub

bigtest/cli.ts at effection-v2 · thefrontside/bigtest

Ensure your React/Vue/Ember/anything app works perfectly across browsers. - bigtest/cli.ts at effection-v2 · thefrontside/bigtest