Home
Support Forums

Build failing with gatsby-source-wordpress-experimental

Hi

In my local machine, build works fine. But on Netlify, it fails. Seems like it doesn’t like downloading too many things? or maybe Wordpress rate limits or something?

... other logs.... 
success  gatsby-source-wordpress  Tag - 1.449s - fetched 35
12:58:13 PM: success  gatsby-source-wordpress  Page - 1.662s - fetched 14
12:58:13 PM: success  gatsby-source-wordpress  Post - 2.175s - fetched 29
12:58:28 PM: error Processing /opt/build/repo/.cache/caches/gatsby-source-wordpress-experimental/6fd9d2b07592f73d9ec14d988dd64e89/Webinar-week-5.png failed
12:58:28 PM: Original error:
12:58:28 PM: 
12:58:28 PM: 
12:58:28 PM:   WorkerError: Processing /opt/build/repo/.cache/caches/gatsby-source-wordpress-  experimental/6fd9d2b07592f73d9ec14d988dd64e89/Webinar-week-5.png failed
12:58:28 PM:   Original error:
12:58:28 PM:   
12:58:28 PM:   - jobs-manager.ts:318 enqueueJob
12:58:28 PM:     [repo]/[gatsby]/src/utils/jobs-manager.ts:318:21
12:58:28 PM:   
12:58:28 PM:   - next_tick.js:68 process._tickCallback
12:58:28 PM:     internal/process/next_tick.js:68:7
12:58:28 PM:   
12:58:28 PM: 
12:58:28 PM: not finished source and transform nodes - 16.798s
12:58:28 PM: not finished  gatsby-source-wordpress  fetching nodes - 16.719s - 116 total
12:58:28 PM: not finished  gatsby-source-wordpress  creating nodes - 14.538s
12:58:28 PM: not finished  gatsby-source-wordpress  MediaItem - 14.538s - fetched 20
12:58:28 PM: not finished Downloading remote files - 13.698s
12:58:28 PM: not finished Generating image thumbnails - 12.889s
12:58:28 PM: npm ERR! code ELIFECYCLE
12:58:28 PM: npm ERR! errno 1
12:58:28 PM: npm ERR! involved-fathers@0.1.0 build: `gatsby build`
12:58:28 PM: npm ERR! Exit status 1
12:58:28 PM: npm ERR!
12:58:28 PM: npm ERR! Failed at the involved-fathers@0.1.0 build script.
12:58:28 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
12:58:28 PM: npm ERR! A complete log of this run can be found in:
12:58:28 PM: npm ERR!     /opt/buildhome/.npm/_logs/2020-09-01T11_58_28_598Z-debug.log
12:58:28 PM: ​
12:58:28 PM: ┌─────────────────────────────┐
12:58:28 PM: │   "build.command" failed    │
12:58:28 PM: └─────────────────────────────┘
12:58:28 PM: ​
12:58:28 PM:   Error message
12:58:28 PM:   Command failed with exit code 1: npm run build
12:58:28 PM: ​
12:58:28 PM:   Error location
12:58:28 PM:   In Build command from Netlify app:
12:58:28 PM:   npm run build
12:58:28 PM: ​
12:58:28 PM:   Resolved config
12:58:28 PM:   build:
12:58:28 PM:     command: npm run build
12:58:28 PM:     commandOrigin: ui
12:58:28 PM:     publish: /opt/build/repo/public
12:58:29 PM: Caching artifacts
12:58:29 PM: Started saving node modules

If it works locally but not at Netlify, you want to check your dependency versions. The following guide explains it better than I could!

Hi. I am having a similar issue. I had a working build for a couple of months and then, yesterday, it began to repeatedly fail to rebuild. No code changes had been made, just content additions in the WordPress CMS.

I contacted the gatsby-source-wordpress-experimental dev [https://github.com/gatsbyjs/gatsby-source-wordpress-experimental/issues/186](Github issue) and he suggested that it is an issue with the site being rate limited. He recommended I request the build server be whitelisted or for rate limiting to be turned off.

Are either of these possible with a Pro account?

Log below:

9:30:04 PM: Build ready to start
9:30:05 PM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
9:30:05 PM: build-image tag: v3.4.1
9:30:05 PM: buildbot version: 648208d76731cd5bca75c1e9bc99d2032a1f1473
9:30:06 PM: Fetching cached dependencies
9:30:06 PM: Starting to download cache of 793.4MB
9:30:12 PM: Finished downloading cache in 6.494990603s
9:30:12 PM: Starting to extract cache
9:30:26 PM: Finished extracting cache in 13.93448314s
9:30:26 PM: Finished fetching cache in 20.661781503s
9:30:26 PM: Starting to prepare the repo for build
9:30:27 PM: Preparing Git Reference refs/heads/master
9:30:29 PM: Starting build script
9:30:29 PM: Installing dependencies
9:30:29 PM: Python version set to 2.7
9:30:29 PM: Started restoring cached node version
9:30:32 PM: Finished restoring cached node version
9:30:32 PM: v12.18.0 is already installed.
9:30:33 PM: Now using node v12.18.0 (npm v6.14.4)
9:30:33 PM: Started restoring cached build plugins
9:30:33 PM: Finished restoring cached build plugins
9:30:33 PM: Attempting ruby version 2.7.1, read from environment
9:30:35 PM: Using ruby version 2.7.1
9:30:35 PM: Using PHP version 5.6
9:30:35 PM: 5.2 is already installed.
9:30:35 PM: Using Swift version 5.2
9:30:35 PM: Started restoring cached node modules
9:30:35 PM: Finished restoring cached node modules
9:30:35 PM: Started restoring cached go cache
9:30:35 PM: Finished restoring cached go cache
9:30:35 PM: go version go1.14.4 linux/amd64
9:30:35 PM: go version go1.14.4 linux/amd64
9:30:35 PM: Installing missing commands
9:30:35 PM: Verify run directory
9:30:37 PM: ​
9:30:37 PM: ┌─────────────────────────────┐
9:30:37 PM: │        Netlify Build        │
9:30:37 PM: └─────────────────────────────┘
9:30:37 PM: ​
9:30:37 PM: ❯ Version
9:30:37 PM:   @netlify/build 4.0.4
9:30:37 PM: ​
9:30:37 PM: ❯ Flags
9:30:37 PM:   deployId: 5f7247cc0428fd7b048b2827
9:30:37 PM:   mode: buildbot
9:30:37 PM: ​
9:30:37 PM: ❯ Current directory
9:30:37 PM:   /opt/build/repo
9:30:37 PM: ​
9:30:37 PM: ❯ Config file
9:30:37 PM:   No config file was defined: using default values.
9:30:37 PM: ​
9:30:37 PM: ❯ Context
9:30:37 PM:   production
9:30:37 PM: ​
9:30:37 PM: ❯ Loading plugins
9:30:37 PM:    - netlify-plugin-gatsby-cache@0.3.0 from Netlify app
9:30:37 PM:    - netlify-plugin-image-optim@0.3.0 from Netlify app
9:30:37 PM:    - netlify-plugin-inline-source@1.0.4 from Netlify app
9:30:37 PM:    - netlify-plugin-inline-critical-css@1.1.3 from Netlify app
9:30:43 PM: ​
9:30:43 PM: ┌────────────────────────────────────────────────────────┐
9:30:43 PM: │ 1. onPreBuild command from netlify-plugin-gatsby-cache │
9:30:43 PM: └────────────────────────────────────────────────────────┘
9:30:43 PM: ​
9:30:54 PM: Found a Gatsby cache. We’re about to go FAST. ⚡️
9:30:54 PM: ​
9:30:54 PM: (netlify-plugin-gatsby-cache onPreBuild completed in 11.7s)
9:30:54 PM: ​
9:30:54 PM: ┌───────────────────────────────────┐
9:30:54 PM: │ 2. Build command from Netlify app │
9:30:54 PM: └───────────────────────────────────┘
9:30:54 PM: ​
9:30:54 PM: $ GATSBY_CONCURRENT_DOWNLOAD=200 gatsby build
9:30:58 PM: success open and validate gatsby-configs - 0.080s
9:31:02 PM: success load plugins - 1.607s
9:31:02 PM: success onPreInit - 0.017s
9:31:02 PM: success delete html and css files from previous builds - 0.043s
9:31:02 PM: success initialize cache - 0.009s
9:31:02 PM: success copy gatsby files - 0.034s
9:31:02 PM: success onPreBootstrap - 0.015s
9:31:04 PM: ⠀
9:31:04 PM: warning  gatsby-source-wordpress  The remote schema has changed since the last build, re-fetching all data
9:31:04 PM: info  gatsby-source-wordpress  Cached schema md5: 0650e022a08d2819f1bc5aefb8ed8446
9:31:04 PM: info  gatsby-source-wordpress  Remote schema md5: 563bc9df39c9b9039cce8fa9b31b9040
9:31:04 PM: ⠀
9:31:04 PM: success  gatsby-source-wordpress  diff schemas - 0.690s
9:31:06 PM: success  gatsby-source-wordpress  writing GraphQL queries to disk at ./WordPress/GraphQL/ - 0.307s
9:31:06 PM: success  gatsby-source-wordpress  ingest WPGraphQL schema - 3.102s
9:31:06 PM: success createSchemaCustomization - 4.241s
9:31:07 PM: success  gatsby-source-wordpress  Availability - 0.688s - fetched 3
9:31:07 PM: success  gatsby-source-wordpress  Fuel - 0.690s - fetched 2
9:31:07 PM: success  gatsby-source-wordpress  Make - 0.715s - fetched 5
9:31:07 PM: success  gatsby-source-wordpress  Comment - 0.815s - fetched 0
9:31:07 PM: success  gatsby-source-wordpress  Menu - 0.877s - fetched 2
9:31:07 PM: success  gatsby-source-wordpress  Category - 0.973s - fetched 4
9:31:08 PM: success  gatsby-source-wordpress  PostFormat - 1.000s - fetched 0
9:31:08 PM: success  gatsby-source-wordpress  ContentType - 1.024s - fetched 4
9:31:08 PM: success  gatsby-source-wordpress  MenuItem - 1.175s - fetched 18
9:31:08 PM: success  gatsby-source-wordpress  Taxonomy - 1.234s - fetched 8
9:31:08 PM: success  gatsby-source-wordpress  UserRole - 1.276s - fetched 0
9:31:08 PM: success  gatsby-source-wordpress  Tag - 1.305s - fetched 0
9:31:08 PM: success  gatsby-source-wordpress  User - 1.410s - fetched 2
9:31:08 PM: success  gatsby-source-wordpress  Car - 1.436s - fetched 6
9:31:08 PM: success  gatsby-source-wordpress  Page - 1.549s - fetched 10
9:31:13 PM: success  gatsby-source-wordpress  Post - 6.378s - fetched 82
9:31:13 PM: success  gatsby-source-wordpress  MediaItem - 0.173s - fetched 0
9:31:13 PM: success  gatsby-source-wordpress  creating nodes - 0.174s
9:31:13 PM: success  gatsby-source-wordpress  fetching nodes - 6.559s - 146 total
9:31:14 PM: success  gatsby-source-wordpress  fetch root fields - 0.486s
9:31:14 PM: success Checking for changed pages - 0.000s
9:31:14 PM: success source and transform nodes - 7.339s
9:31:14 PM: success building schema - 0.804s
9:31:15 PM: success createPages - 0.215s
9:31:15 PM: success Checking for changed pages - 0.000s
9:31:15 PM: success createPagesStatefully - 0.136s
9:31:15 PM: success updating schema - 0.098s
9:31:15 PM: success onPreExtractQueries - 0.001s
9:31:16 PM: success extract queries from components - 1.261s
9:31:16 PM: success write out redirect data - 0.002s
9:31:17 PM: success Build manifest and related icons - 0.358s
9:31:17 PM: success onPostBootstrap - 0.360s
9:31:17 PM: info bootstrap finished - 22.203s
9:31:17 PM: error (node:1311) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
9:31:17 PM: success run static queries - 0.903s - 3/3 3.32/s
9:31:19 PM: success Downloading remote files - 2.349s - 1/1 0.43/s
9:31:20 PM: error  gatsby-source-wordpress  Request failed with status code 429
9:31:20 PM: Error occured while updating a single "mediaItem" node.
9:31:20 PM: GraphQL request to https://headless.apsspecialistvehicles.co.uk/wp/graphql failed.
9:31:20 PM: Please ensure the following statements are true
9:31:20 PM:   - your WordPress URL is correct in gatsby-config.js
9:31:20 PM:   - your server is responding to requests
9:31:20 PM:   - WPGraphQL and WPGatsby are installed in your WordPress backend
9:31:20 PM: not finished run page queries - 2.403s
9:31:20 PM: ​
9:31:20 PM: ┌─────────────────────────────┐
9:31:20 PM: │   "build.command" failed    │
9:31:20 PM: └─────────────────────────────┘
9:31:20 PM: ​
9:31:20 PM:   Error message
9:31:20 PM:   Command failed with exit code 1: GATSBY_CONCURRENT_DOWNLOAD=200 gatsby build
9:31:20 PM: ​
9:31:20 PM:   Error location
9:31:20 PM:   In Build command from Netlify app:
9:31:20 PM:   GATSBY_CONCURRENT_DOWNLOAD=200 gatsby build
9:31:20 PM: ​
9:31:20 PM:   Resolved config
9:31:20 PM:   build:
9:31:20 PM:     command: GATSBY_CONCURRENT_DOWNLOAD=200 gatsby build
9:31:20 PM:     commandOrigin: ui
9:31:20 PM:     environment:
9:31:20 PM:       - GATSBY_WPGRAPHQL_URL
9:31:20 PM:     publish: /opt/build/repo/public
9:31:20 PM:   plugins:
9:31:20 PM:     - inputs: {}
9:31:20 PM:       origin: ui
9:31:20 PM:       package: netlify-plugin-gatsby-cache
9:31:20 PM:     - inputs: {}
9:31:20 PM:       origin: ui
9:31:20 PM:       package: netlify-plugin-image-optim
9:31:20 PM:     - inputs: {}
9:31:20 PM:       origin: ui
9:31:20 PM:       package: netlify-plugin-inline-source
9:31:20 PM:     - inputs: {}
9:31:20 PM:       origin: ui
9:31:20 PM:       package: netlify-plugin-inline-critical-css
9:31:20 PM: Caching artifacts
9:31:20 PM: Started saving node modules
9:31:20 PM: Finished saving node modules
9:31:20 PM: Started saving build plugins
9:31:20 PM: Finished saving build plugins
9:31:20 PM: Started saving pip cache
9:31:20 PM: Finished saving pip cache
9:31:20 PM: Started saving emacs cask dependencies
9:31:20 PM: Finished saving emacs cask dependencies
9:31:20 PM: Started saving maven dependencies
9:31:20 PM: Finished saving maven dependencies
9:31:20 PM: Started saving boot dependencies
9:31:21 PM: Finished saving boot dependencies
9:31:21 PM: Started saving go dependencies
9:31:21 PM: Finished saving go dependencies
9:31:21 PM: Error running command: Build script returned non-zero exit code: 2
9:31:21 PM: Failing build: Failed to build site
9:31:21 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2
9:31:21 PM: Finished processing build request in 1m15.122357443s

If you set this to 5, how does it perform?

Hi. It failed again.

10:44:32 AM: Build ready to start
10:44:34 AM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
10:44:34 AM: build-image tag: v3.4.1
10:44:34 AM: buildbot version: c14f8ac04f7535496782ceb786d06f5741c8ed0f
10:44:34 AM: Fetching cached dependencies
10:44:34 AM: Starting to download cache of 793.4MB
10:44:40 AM: Finished downloading cache in 5.757653935s
10:44:40 AM: Starting to extract cache
10:44:55 AM: Finished extracting cache in 15.134365038s
10:44:55 AM: Finished fetching cache in 21.322111089s
10:44:55 AM: Starting to prepare the repo for build
10:44:56 AM: Preparing Git Reference refs/heads/master
10:44:58 AM: Starting build script
10:44:58 AM: Installing dependencies
10:44:58 AM: Python version set to 2.7
10:44:59 AM: Started restoring cached node version
10:45:02 AM: Finished restoring cached node version
10:45:03 AM: v12.18.0 is already installed.
10:45:03 AM: Now using node v12.18.0 (npm v6.14.4)
10:45:04 AM: Started restoring cached build plugins
10:45:04 AM: Finished restoring cached build plugins
10:45:04 AM: Attempting ruby version 2.7.1, read from environment
10:45:05 AM: Using ruby version 2.7.1
10:45:06 AM: Using PHP version 5.6
10:45:06 AM: 5.2 is already installed.
10:45:06 AM: Using Swift version 5.2
10:45:06 AM: Started restoring cached node modules
10:45:06 AM: Finished restoring cached node modules
10:45:06 AM: Started restoring cached go cache
10:45:06 AM: Finished restoring cached go cache
10:45:06 AM: go version go1.14.4 linux/amd64
10:45:06 AM: go version go1.14.4 linux/amd64
10:45:06 AM: Installing missing commands
10:45:06 AM: Verify run directory
10:45:08 AM: ​
10:45:08 AM: ┌─────────────────────────────┐
10:45:08 AM: │        Netlify Build        │
10:45:08 AM: └─────────────────────────────┘
10:45:08 AM: ​
10:45:08 AM: ❯ Version
10:45:08 AM:   @netlify/build 4.4.0
10:45:08 AM: ​
10:45:08 AM: ❯ Flags
10:45:08 AM:   deployId: 5f730200f9b7ec605701692e
10:45:08 AM:   mode: buildbot
10:45:08 AM: ​
10:45:08 AM: ❯ Current directory
10:45:08 AM:   /opt/build/repo
10:45:08 AM: ​
10:45:08 AM: ❯ Config file
10:45:08 AM:   No config file was defined: using default values.
10:45:08 AM: ​
10:45:08 AM: ❯ Context
10:45:08 AM:   production
10:45:08 AM: ​
10:45:08 AM: ❯ Loading plugins
10:45:08 AM:    - netlify-plugin-gatsby-cache@0.3.0 from Netlify app
10:45:08 AM:    - netlify-plugin-image-optim@0.3.0 from Netlify app
10:45:08 AM:    - netlify-plugin-inline-source@1.0.4 from Netlify app
10:45:08 AM:    - netlify-plugin-inline-critical-css@1.1.3 from Netlify app
10:45:14 AM: ​
10:45:14 AM: ┌────────────────────────────────────────────────────────┐
10:45:14 AM: │ 1. onPreBuild command from netlify-plugin-gatsby-cache │
10:45:14 AM: └────────────────────────────────────────────────────────┘
10:45:14 AM: ​
10:45:27 AM: Found a Gatsby cache. We’re about to go FAST. ⚡️
10:45:28 AM: ​
10:45:28 AM: (netlify-plugin-gatsby-cache onPreBuild completed in 13.1s)
10:45:28 AM: ​
10:45:28 AM: ┌───────────────────────────────────┐
10:45:28 AM: │ 2. Build command from Netlify app │
10:45:28 AM: └───────────────────────────────────┘
10:45:28 AM: ​
10:45:28 AM: $ GATSBY_CONCURRENT_DOWNLOAD=5 gatsby build
10:45:31 AM: success open and validate gatsby-configs - 0.072s
10:45:36 AM: success load plugins - 1.670s
10:45:36 AM: success onPreInit - 0.021s
10:45:36 AM: success delete html and css files from previous builds - 0.040s
10:45:36 AM: success initialize cache - 0.008s
10:45:36 AM: success copy gatsby files - 0.053s
10:45:36 AM: success onPreBootstrap - 0.020s
10:45:39 AM: ⠀
10:45:39 AM: warning  gatsby-source-wordpress  The remote schema has changed since the last build, re-fetching all data
10:45:39 AM: info  gatsby-source-wordpress  Cached schema md5: 0650e022a08d2819f1bc5aefb8ed8446
10:45:39 AM: info  gatsby-source-wordpress  Remote schema md5: 563bc9df39c9b9039cce8fa9b31b9040
10:45:39 AM: ⠀
10:45:39 AM: success  gatsby-source-wordpress  diff schemas - 1.192s
10:45:42 AM: success  gatsby-source-wordpress  writing GraphQL queries to disk at ./WordPress/GraphQL/ - 0.439s
10:45:42 AM: success  gatsby-source-wordpress  ingest WPGraphQL schema - 4.081s
10:45:42 AM: success createSchemaCustomization - 6.192s
10:45:43 AM: success  gatsby-source-wordpress  Availability - 0.553s - fetched 3
10:45:43 AM: success  gatsby-source-wordpress  Make - 0.576s - fetched 5
10:45:43 AM: success  gatsby-source-wordpress  Category - 0.752s - fetched 4
10:45:43 AM: success  gatsby-source-wordpress  Fuel - 0.868s - fetched 2
10:45:44 AM: success  gatsby-source-wordpress  Car - 1.678s - fetched 7
10:45:44 AM: success  gatsby-source-wordpress  Comment - 0.534s - fetched 0
10:45:45 AM: success  gatsby-source-wordpress  MenuItem - 0.639s - fetched 18
10:45:45 AM: success  gatsby-source-wordpress  ContentType - 0.643s - fetched 4
10:45:45 AM: success  gatsby-source-wordpress  Menu - 0.697s - fetched 2
10:45:45 AM: success  gatsby-source-wordpress  PostFormat - 0.768s - fetched 0
10:45:45 AM: success  gatsby-source-wordpress  Page - 0.889s - fetched 10
10:45:46 AM: success  gatsby-source-wordpress  Taxonomy - 0.914s - fetched 8
10:45:46 AM: success  gatsby-source-wordpress  Tag - 0.985s - fetched 0
10:45:53 AM: success  gatsby-source-wordpress  Post - 8.538s - fetched 82
10:45:54 AM: success  gatsby-source-wordpress  UserRole - 0.527s - fetched 0
10:45:54 AM: success  gatsby-source-wordpress  User - 0.602s - fetched 2
10:45:55 AM: error (node:1311) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
10:46:13 AM: success  gatsby-source-wordpress  MediaItem - 19.238s - fetched 21
10:46:13 AM: success  gatsby-source-wordpress  creating nodes - 19.240s
10:46:13 AM: success  gatsby-source-wordpress  fetching nodes - 30.764s - 168 total
10:46:15 AM: success  gatsby-source-wordpress  fetch root fields - 1.838s
10:46:15 AM: success Downloading remote files - 19.652s - 21/1438 73.17/s
10:46:15 AM: success Checking for changed pages - 0.000s
10:46:15 AM: success source and transform nodes - 32.917s
10:46:16 AM: success building schema - 0.825s
10:46:16 AM: success createPages - 0.215s
10:46:16 AM: success Checking for changed pages - 0.000s
10:46:16 AM: success createPagesStatefully - 0.157s
10:46:16 AM: success updating schema - 0.088s
10:46:16 AM: success onPreExtractQueries - 0.001s
10:46:18 AM: success extract queries from components - 1.307s
10:46:18 AM: success write out redirect data - 0.001s
10:46:18 AM: success Build manifest and related icons - 0.189s
10:46:18 AM: success onPostBootstrap - 0.191s
10:46:18 AM: info bootstrap finished - 50.205s
10:46:19 AM: success run static queries - 1.177s - 3/3 2.55/s
10:46:21 AM: success Downloading remote files - 2.476s - 1/1 0.40/s
10:46:22 AM: error  gatsby-source-wordpress  Request failed with status code 429
10:46:22 AM: Error occured while updating a single "mediaItem" node.
10:46:22 AM: GraphQL request to https://headless.apsspecialistvehicles.co.uk/wp/graphql failed.
10:46:22 AM: Please ensure the following statements are true
10:46:22 AM:   - your WordPress URL is correct in gatsby-config.js
10:46:22 AM:   - your server is responding to requests
10:46:22 AM:   - WPGraphQL and WPGatsby are installed in your WordPress backend
10:46:22 AM: not finished run page queries - 2.808s
10:46:22 AM: not finished Generating image thumbnails - 1.041s
10:46:22 AM: (sharp:1311): GLib-CRITICAL **: 09:46:22.375: g_hash_table_lookup: assertion 'hash_table != NULL' failed
10:46:22 AM: (sharp:1311): GLib-CRITICAL **: 09:46:22.375: g_hash_table_lookup: assertion 'hash_table != NULL' failed
10:46:22 AM: (sharp:1311): GLib-CRITICAL **: 09:46:22.375: g_hash_table_lookup: assertion 'hash_table != NULL' failed
10:46:22 AM: (sharp:1311): GLib-CRITICAL **: 09:46:22.375: g_hash_table_lookup: assertion 'hash_table != NULL' failed
10:46:22 AM: (sharp:1311): GLib-CRITICAL **: 09:46:22.375: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed
10:46:22 AM: (sharp:1311): GLib-CRITICAL **: 09:46:22.375: g_hash_table_lookup: assertion 'hash_table != NULL' failed
10:46:23 AM: ​
10:46:23 AM: ┌─────────────────────────────┐
10:46:23 AM: │   "build.command" failed    │
10:46:23 AM: └─────────────────────────────┘
10:46:23 AM: ​
10:46:23 AM:   Error message
10:46:23 AM:   Command was killed with SIGSEGV (Segmentation fault): GATSBY_CONCURRENT_DOWNLOAD=5 gatsby build
10:46:23 AM: ​
10:46:23 AM:   Error location
10:46:23 AM:   In Build command from Netlify app:
10:46:23 AM:   GATSBY_CONCURRENT_DOWNLOAD=5 gatsby build
10:46:23 AM: ​
10:46:23 AM:   Resolved config
10:46:23 AM:   build:
10:46:23 AM:     command: GATSBY_CONCURRENT_DOWNLOAD=5 gatsby build
10:46:23 AM:     commandOrigin: ui
10:46:23 AM:     environment:
10:46:23 AM:       - GATSBY_WPGRAPHQL_URL
10:46:23 AM:     publish: /opt/build/repo/public
10:46:23 AM:   plugins:
10:46:23 AM:     - inputs: {}
10:46:23 AM:       origin: ui
10:46:23 AM:       package: netlify-plugin-gatsby-cache
10:46:23 AM:     - inputs: {}
10:46:23 AM:       origin: ui
10:46:23 AM:       package: netlify-plugin-image-optim
10:46:23 AM:     - inputs: {}
10:46:23 AM:       origin: ui
10:46:23 AM:       package: netlify-plugin-inline-source
10:46:23 AM:     - inputs: {}
10:46:23 AM:       origin: ui
10:46:23 AM:       package: netlify-plugin-inline-critical-css
10:46:24 AM: Caching artifacts
10:46:24 AM: Started saving node modules
10:46:24 AM: Finished saving node modules
10:46:24 AM: Started saving build plugins
10:46:24 AM: Finished saving build plugins
10:46:24 AM: Started saving pip cache
10:46:24 AM: Finished saving pip cache
10:46:24 AM: Started saving emacs cask dependencies
10:46:24 AM: Finished saving emacs cask dependencies
10:46:24 AM: Started saving maven dependencies
10:46:24 AM: Finished saving maven dependencies
10:46:24 AM: Started saving boot dependencies
10:46:24 AM: Finished saving boot dependencies
10:46:24 AM: Started saving go dependencies
10:46:24 AM: Finished saving go dependencies
10:46:24 AM: Error running command: Build script returned non-zero exit code: 2
10:46:24 AM: Failing build: Failed to build site
10:46:24 AM: Failed during stage 'building site': Build script returned non-zero exit code: 2
10:46:24 AM: Finished processing build request in 1m49.974535123s

I think I might be misunderstanding, in fact! Looks like a rate limit possibly imposed by your WordPress host. Sorry to have to do this but can you ensure that they’re not rate limiting calls?

I will check with my WordPress host, however I’m able to build the site without issue in my local environment, which suggests the WordPress host isn’t affecting it.

Hi. This is the response from my WordPress host.

Would you be able to slow down the responses or would I need to request that from the gatsby-source-wordpress-experimental developer?

Thanks

I have been able to resolve this issue by putting a limit on the ‘Posts’ that are requested, using the below:

type: {
    Post: {
       limit:50
    },
},

This does result in some of the older posts not being pulled into the site, but at least the new posts are now being pulled in.

Thanks for your help.

Hi, @satcreative, we don’t have a way to slow down the site build code. The code will need to do this itself if that is required.

One solution would be to add an option to the plugin to add a delay before each request. For example, optionally using setTimeout() ​ with a configurable value for the delay to any API requests.

Again, this would all need to be done in the build code itself and we don’t control that code. These are changes you (or the plugin developer) would need to make.

If there are other questions, please let us know.

I’m having a similar issue (I think)

Any ideas on how to fix would be appreciated.

3:03:49 PM: Build ready to start
3:03:53 PM: build-image version: 09c2cdcdf242cf2f57c9ee0fcad9d298fad9ad41
3:03:53 PM: build-image tag: v3.5.0
3:03:53 PM: buildbot version: 8df8a50b1177b0b57364d20e0ea150448924cebf
3:03:53 PM: Building without cache
3:03:53 PM: Starting to prepare the repo for build
3:03:53 PM: No cached dependencies found. Cloning fresh repo
3:03:53 PM: git clone https://github.com/RyanPinPB/pdm-gatsby
3:03:56 PM: Preparing Git Reference refs/heads/master
3:03:58 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'public' versus 'public/' in the Netlify UI
3:03:58 PM: Starting build script
3:03:58 PM: Installing dependencies
3:03:58 PM: Python version set to 2.7
3:04:00 PM: v12.18.0 is already installed.
3:04:01 PM: Now using node v12.18.0 (npm v6.14.4)
3:04:01 PM: Started restoring cached build plugins
3:04:01 PM: Finished restoring cached build plugins
3:04:01 PM: Attempting ruby version 2.7.1, read from environment
3:04:03 PM: Using ruby version 2.7.1
3:04:03 PM: Using PHP version 5.6
3:04:03 PM: Started restoring cached node modules
3:04:03 PM: Finished restoring cached node modules
3:04:04 PM: Installing NPM modules using NPM version 6.14.4
3:05:02 PM: > yarn@1.22.10 preinstall /opt/build/repo/node_modules/yarn
3:05:02 PM: > :; (node ./preinstall.js > /dev/null 2>&1 || true)
3:05:07 PM: > bufferutil@4.0.2 install /opt/build/repo/node_modules/bufferutil
3:05:07 PM: > node-gyp-build
3:05:08 PM: > utf-8-validate@5.0.3 install /opt/build/repo/node_modules/utf-8-validate
3:05:08 PM: > node-gyp-build
3:05:09 PM: > sharp@0.26.3 install /opt/build/repo/node_modules/gatsby-plugin-manifest/node_modules/sharp
3:05:09 PM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
3:05:10 PM: info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.10.0/libvips-8.10.0-linux-x64.tar.br
3:05:13 PM: > sharp@0.26.3 install /opt/build/repo/node_modules/gatsby-plugin-sharp/node_modules/sharp
3:05:13 PM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
3:05:15 PM: info sharp Using cached /opt/buildhome/.npm/_libvips/libvips-8.10.0-linux-x64.tar.br
3:05:17 PM: > sharp@0.25.4 install /opt/build/repo/node_modules/sharp
3:05:17 PM: > (node install/libvips && node install/dll-copy && prebuild-install --runtime=napi) || (node-gyp rebuild && node install/dll-copy)
3:05:18 PM: info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.9.1/libvips-8.9.1-linux-x64.tar.gz
3:05:20 PM: > node-sass@4.14.1 install /opt/build/repo/node_modules/node-sass
3:05:20 PM: > node scripts/install.js
3:05:20 PM: Downloading binary from https://github.com/sass/node-sass/releases/download/v4.14.1/linux-x64-72_binding.node
3:05:21 PM: Download complete
3:05:21 PM: Binary saved to /opt/build/repo/node_modules/node-sass/vendor/linux-x64-72/binding.node
3:05:21 PM: Caching binary to /opt/buildhome/.npm/node-sass/4.14.1/linux-x64-72_binding.node
3:05:22 PM: > core-js@2.6.11 postinstall /opt/build/repo/node_modules/core-js
3:05:22 PM: > node -e "try{require('./postinstall')}catch(e){}"
3:05:22 PM: > core-js-pure@3.7.0 postinstall /opt/build/repo/node_modules/core-js-pure
3:05:22 PM: > node -e "try{require('./postinstall')}catch(e){}"
3:05:22 PM: > core-js@3.7.0 postinstall /opt/build/repo/node_modules/gatsby/node_modules/core-js
3:05:22 PM: > node -e "try{require('./postinstall')}catch(e){}"
3:05:23 PM: > gatsby-telemetry@1.5.0 postinstall /opt/build/repo/node_modules/gatsby-telemetry
3:05:23 PM: > node src/postinstall.js || true
3:05:23 PM: > mozjpeg@7.0.0 postinstall /opt/build/repo/node_modules/mozjpeg
3:05:23 PM: > node lib/install.js
3:05:24 PM:   ✔ mozjpeg pre-build test passed successfully
3:05:24 PM: > pngquant-bin@6.0.0 postinstall /opt/build/repo/node_modules/pngquant-bin
3:05:24 PM: > node lib/install.js
3:05:24 PM:   ✔ pngquant pre-build test passed successfully
3:05:24 PM: > gatsby-cli@2.14.0 postinstall /opt/build/repo/node_modules/gatsby/node_modules/gatsby-cli
3:05:24 PM: > node scripts/postinstall.js
3:05:25 PM: > gatsby@2.27.1 postinstall /opt/build/repo/node_modules/gatsby
3:05:25 PM: > node scripts/postinstall.js
3:05:25 PM: > node-sass@4.14.1 postinstall /opt/build/repo/node_modules/node-sass
3:05:25 PM: > node scripts/build.js
3:05:25 PM: Binary found at /opt/build/repo/node_modules/node-sass/vendor/linux-x64-72/binding.node
3:05:25 PM: Testing binary
3:05:25 PM: Binary is fine
3:05:28 PM: npm WARN using-gatsby-source-wordpress-experimental@0.0.1 No repository field.
3:05:28 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/fsevents):
3:05:28 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
3:05:28 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/chokidar/node_modules/fsevents):
3:05:28 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
3:05:28 PM: added 2532 packages from 1346 contributors and audited 2537 packages in 83.748s
3:05:31 PM: 154 packages are looking for funding
3:05:31 PM:   run `npm fund` for details
3:05:31 PM: found 0 vulnerabilities
3:05:31 PM: NPM modules installed
3:05:31 PM: Started restoring cached go cache
3:05:31 PM: Finished restoring cached go cache
3:05:31 PM: go version go1.14.4 linux/amd64
3:05:31 PM: go version go1.14.4 linux/amd64
3:05:31 PM: Installing missing commands
3:05:31 PM: Verify run directory
3:05:33 PM: ​
3:05:33 PM: ────────────────────────────────────────────────────────────────
3:05:33 PM:   Netlify Build                                                 
3:05:33 PM: ────────────────────────────────────────────────────────────────
3:05:33 PM: ​
3:05:33 PM: ❯ Version
3:05:33 PM:   @netlify/build 5.3.3
3:05:33 PM: ​
3:05:33 PM: ❯ Flags
3:05:33 PM:   deployId: 5fbd91550c1c1900fc89ef34
3:05:33 PM:   mode: buildbot
3:05:33 PM: ​
3:05:33 PM: ❯ Current directory
3:05:33 PM:   /opt/build/repo
3:05:33 PM: ​
3:05:33 PM: ❯ Config file
3:05:33 PM:   No config file was defined: using default values.
3:05:33 PM: ​
3:05:33 PM: ❯ Context
3:05:33 PM:   production
3:05:33 PM: ​
3:05:33 PM: ────────────────────────────────────────────────────────────────
3:05:33 PM:   1. Build command from Netlify app                             
3:05:33 PM: ────────────────────────────────────────────────────────────────
3:05:33 PM: ​
3:05:33 PM: $ gatsby build
3:05:37 PM: success open and validate gatsby-configs - 0.061s
3:05:38 PM: success load plugins - 1.345s
3:05:38 PM: plugin-netlify-cache: Restoring 0 cached files for .cache directory with 0 already existing files.
3:05:38 PM: plugin-netlify-cache: Netlify cache restored
3:05:38 PM: success onPreInit - 0.157s
3:05:38 PM: success delete html and css files from previous builds - 0.004s
3:05:38 PM: success initialize cache - 0.007s
3:05:38 PM: success copy gatsby files - 0.032s
3:05:38 PM: success onPreBootstrap - 0.017s
3:05:41 PM: ⠀
3:05:41 PM: info  gatsby-source-wordpress 
3:05:41 PM: 	This is either your first build or the cache was cleared.
3:05:41 PM: 	Please wait while your WordPress data is synced to your Gatsby cache.
3:05:41 PM: 	Maybe now's a good time to get up and stretch? :D
3:05:43 PM: success  gatsby-source-wordpress  writing GraphQL queries to disk at ./WordPress/GraphQL/ - 0.222s
3:05:43 PM: success  gatsby-source-wordpress  ingest WPGraphQL schema - 2.536s
3:05:43 PM: success createSchemaCustomization - 4.542s
3:05:44 PM: success  gatsby-source-wordpress  UserRole - 1.017s - fetched 0
3:05:45 PM: success  gatsby-source-wordpress  User - 1.125s - fetched 1
3:05:46 PM: success  gatsby-source-wordpress  fetch root fields - 2.570s
3:05:46 PM: success  gatsby-source-wordpress  Comment - 2.806s - fetched 1
3:05:46 PM: success  gatsby-source-wordpress  PostFormat - 2.806s - fetched 0
3:05:46 PM: success  gatsby-source-wordpress  Tag - 2.822s - fetched 0
3:05:46 PM: success  gatsby-source-wordpress  Taxonomy - 2.832s - fetched 3
3:05:46 PM: success  gatsby-source-wordpress  Category - 2.861s - fetched 1
3:05:46 PM: success  gatsby-source-wordpress  Menu - 2.883s - fetched 2
3:05:46 PM: success  gatsby-source-wordpress  ContentType - 2.906s - fetched 3
3:05:46 PM: success  gatsby-source-wordpress  Post - 2.931s - fetched 2
3:05:46 PM: success  gatsby-source-wordpress  Page - 2.946s - fetched 6
3:05:46 PM: success  gatsby-source-wordpress  MenuItem - 2.963s - fetched 10
3:05:47 PM: success  gatsby-source-wordpress  MediaItem - 1.041s - fetched 1
3:05:47 PM: success  gatsby-source-wordpress  creating nodes - 1.042s
3:05:47 PM: success  gatsby-source-wordpress  fetching nodes - 4.010s - 30 total
3:05:47 PM: success Downloading remote files - 0.390s - 1/1 2.57/s
3:05:47 PM: success Checking for changed pages - 0.000s
3:05:47 PM: success source and transform nodes - 4.381s
3:05:48 PM: success building schema - 0.732s
3:05:48 PM: info Total nodes: 149, SitePage nodes: 9 (use --verbose for breakdown)
3:05:48 PM: success createPages - 0.058s
3:05:48 PM: success Checking for changed pages - 0.000s
3:05:48 PM: success createPagesStatefully - 0.091s
3:05:48 PM: success update schema - 0.037s
3:05:48 PM: success onPreExtractQueries - 0.001s
3:05:49 PM: warning Using the global `graphql` tag is deprecated, and will not be supported in v3.
3:05:49 PM: Import it instead like:  import { graphql } from 'gatsby' in file:
3:05:49 PM: /opt/build/repo/src/pages/projects.js
3:05:50 PM: success extract queries from components - 1.198s
3:05:50 PM: warning The GraphQL query in the non-page component "/opt/build/repo/src/templates/single/Page.js" will not be run.
3:05:50 PM: Exported queries are only executed for Page components. It's possible you're
3:05:50 PM: trying to create pages in your gatsby-node.js and that's failing for somereason.
3:05:50 PM: If the failing component(s) is a regular component and not intended to be a page
3:05:50 PM: component, you generally want to use a <StaticQuery> (https://gatsbyjs.org/docs/static-query)
3:05:50 PM: instead of exporting a page query.
3:05:50 PM: If you're more experienced with GraphQL, you can also export GraphQLfragments from components and compose the fragments in the Page component
3:05:50 PM: query and pass data down into the child component — https://graphql.org/learn/queries/#fragments
3:05:50 PM: success write out redirect data - 0.001s
3:05:50 PM: vips_value_hash: no case for NULL
3:05:50 PM: 	type 64, gchararray
3:05:50 PM: 	generic 53, GParamString
3:05:50 PM: vips_value_hash: no case for 0.000000
3:05:50 PM: 	type 60, gdouble
3:05:50 PM: 	generic 109, GParamDouble
3:05:50 PM: vips_value_hash: no case for FALSE
3:05:50 PM: 	type 20, gboolean
3:05:50 PM: 	generic 76, GParamBoolean
3:05:50 PM: vips_value_hash: no case for ((VipsAccess) VIPS_ACCESS_RANDOM)
3:05:50 PM: 	type 66734304, VipsAccess
3:05:50 PM: 	generic 80, GParamEnum
3:05:50 PM: vips_value_hash: no case for FALSE
3:05:50 PM: 	type 20, gboolean
3:05:50 PM: 	generic 76, GParamBoolean
3:05:51 PM: ​
3:05:51 PM: ────────────────────────────────────────────────────────────────
3:05:51 PM:   "build.command" failed                                        
3:05:51 PM: ────────────────────────────────────────────────────────────────
3:05:51 PM: ​
3:05:51 PM:   Error message
3:05:51 PM:   Command was killed with SIGSEGV (Segmentation fault): gatsby build
3:05:51 PM: ​
3:05:51 PM:   Error location
3:05:51 PM:   In Build command from Netlify app:
3:05:51 PM:   gatsby build
3:05:51 PM: ​
3:05:51 PM:   Resolved config
3:05:51 PM:   build:
3:05:51 PM:     command: gatsby build
3:05:51 PM:     commandOrigin: ui
3:05:51 PM:     publish: /opt/build/repo/public
3:05:51 PM: Caching artifacts
3:05:51 PM: Started saving node modules
3:05:51 PM: Finished saving node modules
3:05:51 PM: Started saving build plugins
3:05:51 PM: Finished saving build plugins
3:05:51 PM: Started saving pip cache
3:05:51 PM: Finished saving pip cache
3:05:51 PM: Started saving emacs cask dependencies
3:05:51 PM: Finished saving emacs cask dependencies
3:05:51 PM: Started saving maven dependencies
3:05:51 PM: Finished saving maven dependencies
3:05:51 PM: Started saving boot dependencies
3:05:51 PM: Finished saving boot dependencies
3:05:51 PM: Started saving go dependencies
3:05:51 PM: Finished saving go dependencies
3:05:54 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
3:05:54 PM: Failing build: Failed to build site
3:05:54 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2
3:05:54 PM: Finished processing build request in 2m1.470756566s

Hi, @RyanPinPB. This is a public repo so I cloned it and installed the name version of node. Then I ran npm install and npm run build. This was the output of the build command for me locally (meaning outside of Netlify):

$ npm run build

> using-gatsby-source-wordpress-experimental@0.0.1 build /home/username/tmp/pdm-gatsby
> gatsby build

╔════════════════════════════════════════════════════════════════════════╗
║                                                                        ║
║   Gatsby collects anonymous usage analytics                            ║
║   to help improve Gatsby for all users.                                ║
║                                                                        ║
║   If you'd like to opt-out, you can use `gatsby telemetry --disable`   ║
║   To learn more, checkout https://gatsby.dev/telemetry                 ║
║                                                                        ║
╚════════════════════════════════════════════════════════════════════════╝
success open and validate gatsby-configs - 0.055s
success load plugins - 0.989s
success onPreInit - 0.036s
success delete html and css files from previous builds - 0.003s
success initialize cache - 0.006s
success copy gatsby files - 0.022s
success onPreBootstrap - 0.013s
⠀
info  gatsby-source-wordpress

	This is either your first build or the cache was cleared.
	Please wait while your WordPress data is synced to your Gatsby cache.

	Maybe now's a good time to get up and stretch? :D

success  gatsby-source-wordpress  writing GraphQL queries to disk at ./WordPress/GraphQL/ - 0.298s
success  gatsby-source-wordpress  ingest WPGraphQL schema - 2.644s
success createSchemaCustomization - 6.701s
success  gatsby-source-wordpress  Tag - 2.303s - fetched 0
success  gatsby-source-wordpress  UserRole - 2.333s - fetched 0
success  gatsby-source-wordpress  Taxonomy - 2.356s - fetched 3
success  gatsby-source-wordpress  User - 2.549s - fetched 1
success  gatsby-source-wordpress  Page - 2.800s - fetched 6
success  gatsby-source-wordpress  fetch root fields - 3.351s
success  gatsby-source-wordpress  Category - 3.390s - fetched 1
success  gatsby-source-wordpress  ContentType - 3.475s - fetched 3
success  gatsby-source-wordpress  Comment - 3.480s - fetched 1
success  gatsby-source-wordpress  PostFormat - 3.549s - fetched 0
success  gatsby-source-wordpress  Menu - 3.572s - fetched 2
success  gatsby-source-wordpress  Post - 3.646s - fetched 2
success  gatsby-source-wordpress  MenuItem - 3.671s - fetched 10
success  gatsby-source-wordpress  MediaItem - 0.911s - fetched 1
success  gatsby-source-wordpress  creating nodes - 0.915s
success  gatsby-source-wordpress  fetching nodes - 4.594s - 30 total
success Downloading remote files - 0.301s - 1/1 3.33/s
success Checking for changed pages - 0.001s
success source and transform nodes - 5.284s
success building schema - 0.820s
info Total nodes: 149, SitePage nodes: 9 (use --verbose for breakdown)
success createPages - 0.054s
success Checking for changed pages - 0.001s
success createPagesStatefully - 0.116s
success update schema - 0.039s
success onPreExtractQueries - 0.001s
warning Using the global `graphql` tag is deprecated, and will not be supported in v3.
Import it instead like:  import { graphql } from 'gatsby' in file:
/home/username/tmp/pdm-gatsby/src/pages/projects.js
success extract queries from components - 1.296s
warning The GraphQL query in the non-page component "/home/username/tmp/pdm-gatsby/src/templates/single/Page.js" will not be run.
Exported queries are only executed for Page components. It's possible you're
trying to create pages in your gatsby-node.js and that's failing for some
reason.

If the failing component(s) is a regular component and not intended to be a page
component, you generally want to use a <StaticQuery> (https://gatsbyjs.org/docs/static-query)
instead of exporting a page query.

If you're more experienced with GraphQL, you can also export GraphQL
fragments from components and compose the fragments in the Page component
query and pass data down into the child component — https://graphql.org/learn/queries/#fragments
success write out redirect data - 0.018s
⠁ vips_value_hash: no case for NULL
	type 64, gchararray
	generic 53, GParamString
vips_value_hash: no case for 0.000000
	type 60, gdouble
	generic 109, GParamDouble
vips_value_hash: no case for FALSE
	type 20, gboolean
	generic 76, GParamBoolean
vips_value_hash: no case for ((VipsAccess) VIPS_ACCESS_RANDOM)
	type 73595104, VipsAccess
	generic 80, GParamEnum
vips_value_hash: no case for FALSE
	type 20, gboolean
	generic 76, GParamBoolean
Segmentation fault (core dumped)
npm ERR! code ELIFECYCLE
npm ERR! errno 139
npm ERR! using-gatsby-source-wordpress-experimental@0.0.1 build: `gatsby build`
npm ERR! Exit status 139
npm ERR!
npm ERR! Failed at the using-gatsby-source-wordpress-experimental@0.0.1 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/username/.npm/_logs/2020-11-25T08_35_14_599Z-debug.log

As you can see the error is exactly the same:

success write out redirect data - 0.018s
⠁ vips_value_hash: no case for NULL
	type 64, gchararray
	generic 53, GParamString
vips_value_hash: no case for 0.000000
	type 60, gdouble
	generic 109, GParamDouble
vips_value_hash: no case for FALSE
	type 20, gboolean
	generic 76, GParamBoolean
vips_value_hash: no case for ((VipsAccess) VIPS_ACCESS_RANDOM)
	type 73595104, VipsAccess
	generic 80, GParamEnum
vips_value_hash: no case for FALSE
	type 20, gboolean
	generic 76, GParamBoolean
Segmentation fault (core dumped)

In other words, there is some error with your build process but Netlify isn’t causing it. This happens anytime this build is done, not just at Netlify.

Because this isn’t a Netlify specific issue, our support team won’t be able to provide more assistance. Our support scope is limited to Netlify specific issues and this is a bug in third-party code. Our support scope doesn’t include third-party code.

If you resolve the local build issue however and the build at Netlify still fails, please let us know. Also, other people here may be willing to troubleshoot this issue with you and the question is still welcome. It is just that our support team doesn’t have the resources to troubleshoot third-party code. Others are certainly welcome to do so, however.

Thank you @luke for checking on this

I’ll do some more testing.

It builds fine on my local machine which makes me wonder if one of the new updates changed in the package.json file has messed something up

Turns out that it was the auto-deploy from my git push’es that was having a problem.

So something between github and netlify might have caused the issue? I’m not sure

I used Netlify’s CLI and was able to deploy (way faster too)

Hi, @RyanPinPB. When you used Netlify CLI to upload, you skipped the build process at Netlify entirely. This issue definitely (as in 100% without a doubt) was not caused by anything other than the site code itself. I was able to reproduce this in my first local build of this repo and I didn’t use Netlify in any way.

If I can reproduce the error locally and I was not using Netlify in any way, then it is impossible for anything at Netlify to be the root cause. I don’t think is was anything GitHub related either.

Note, your local system is not the “source of truth” for this repository. The upstream repo at GitHub is the source of truth for anyone using that repo. This means that just because it works for you locally doesn’t necessarily mean that your repo works for everyone else that clones it.

It is very common for the local working directory where someone’s repo is cloned to contain many files which are not part of the repo itself (entire directory trees like ./node_modules, local configuration files, etc). This means your local working copy of your repo will almost certainly differ from the repo itself. When you clone and build your repo on another service (like Netlify, CircleCI, Jenkins, etc) that service can only access what is in your repo and it probably will not be identical to your local system.

What I recommend in most cases is for someone to make a fresh clone in a new directory. Then, in this fresh directory, run the dependency install and build (npm install and whatever the build command is). It is also important to be sure the same version of whatever tools are used are installed both places. For example, the build above used node version 12.18.0. If your local version of node is different that could explain the issue. The solution in that case is to change the node version at Netlify to match the local system’s version.

Cloning the repo into a new directory worked for me.

Here’s a vid:

So unless I have something globally installed that’s required, it should work on others. It is wierd that you got the same "vips … . " error

It would be good to find out what that is. I posted in the Gatsby discord channel and on StackOverflow without any help on that yet’

Thanks again for your valuable time Luke.

No problem for me anymore, just for my curiosity at this point