Error: connect ETIMEDOUT

Description

I can’t launch / build the project because the plugin constantly throws ETIMEDOUT error (most often for MediaItem).

Steps to reproduce

Just follow this instruction: https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-wordpress/docs/getting-started.md

gatsby-config.js

{
  resolve: 'gatsby-source-wordpress',
  options: {
    url: process.env.WPGRAPHQL_URL,
  },
}

Then

yarn start

Expected result

Expect that the project will be launched and the requests will be fulfilled.

• how to increase timeout?
• can I possibly skip these errors?

Actual result

Some time for random query:

And for MediaItem (very often)

Environment

What I tried

1. package.json (didn’t help)

"develop": "GATSBY_CONCURRENT_DOWNLOAD=5 gatsby develop",

1. config options (didn’t help)

gatsby-config.js

{
  // ...
  MediaItem: {
    localFile: {
      requestConcurrency: 5,
    },
    lazyNodes: false,
  },
  html: {
    useGatsbyImage: true,
    fallbackImageMaxWidth: 200,
    createStaticFiles: true,
    imageMaxWidth: 756,
  },
  schema: {
    timeout: 3000000,
    requestConcurrency: 5,
  },
  // ...
}

Halp!

[ThyNameIsMud]

Timeouts for creating a new node aren’t directly applied to fetching a remote node. Instead of using gatsby-source-filesystem the gatsby-source-wordpress plugin decided to reimplement it.

https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-remote-file-node/index.js#L58

These timeouts need to be adjustable because there is no one-size-fits-all solution here. These calls ALWAYS fail after a threshold. This is the second time an issue like this has burned me, the first time was from the gatsby-source-filesystem which I submitted the fix for. Now it’s this reimplemented solution that needs it.

[ThyNameIsMud]

node_modules/gatsby-source-wordpress/dist/steps/source-nodes/create-nodes/create-remote-file-node/index.js

Look for got.stream in the file and the timeout associated. Change it to look like

const responseStream = got.stream(url, {
    headers,
    timeout: { send: CONNECTION_TIMEOUT },
    retries: CONNECTION_RETRY_LIMIT,
    ...httpOpts
});

This will have the timeout execute when the socket is connected instead of when it’s queued. The documentation notes how the times are treated: https://github.com/sindresorhus/got/tree/v11.7.0#timeout

You may want to adjust CONNECTION_TIMEOUT or STALL_TIMEOUT as well.

You will want to use something like patch-patch to make the change until this is properly fixed