Error message: Gatsby-plugin-feed

[KarinaFrappier]

Hi all,

I keep getting the same error message when I try to upload an article to my blog. The error reads as follows: “gatsby-plugin-feed was initialized in gatsby-config.js without a title in a feed.
This means that the plugin will use the default feed title, which may not match your use case. This behavior will be removed in the next major release of gatsby-plugin-feed.”

This error message started not too long ago but I can’t tell that I’m doing anything differently than my prior uploads. Would anyone be able to tell me what this means and what I can do to fix it? I have attached the deploy log:

11:26:55 AM: Build ready to start
11:26:57 AM: build-image version: ca811f47d4c1cbd1812d1eb6ecb0c977e86d1a1d
11:26:57 AM: build-image tag: v3.3.20
11:26:57 AM: buildbot version: be8ecf2af866e16fa4301cc5c14de2ccbbb21cf4
11:26:57 AM: Fetching cached dependencies
11:26:57 AM: Starting to download cache of 399.4MB
11:26:59 AM: Finished downloading cache in 1.591225466s
11:26:59 AM: Starting to extract cache
11:27:16 AM: Finished extracting cache in 17.289492737s
11:27:16 AM: Finished fetching cache in 18.972780802s
11:27:16 AM: Starting to prepare the repo for build
11:27:16 AM: Preparing Git Reference refs/heads/master
11:27:18 AM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘public’ versus ‘public/’ in the Netlify UI
11:27:18 AM: Starting build script
11:27:18 AM: Installing dependencies
11:27:18 AM: Python version set to 2.7
11:27:19 AM: Started restoring cached node version
11:27:22 AM: Finished restoring cached node version
11:27:22 AM: v10.22.0 is already installed.
11:27:23 AM: Now using node v10.22.0 (npm v6.14.6)
11:27:23 AM: Started restoring cached build plugins
11:27:23 AM: Finished restoring cached build plugins
11:27:23 AM: Attempting ruby version 2.6.2, read from environment
11:27:24 AM: Using ruby version 2.6.2
11:27:25 AM: Using PHP version 5.6
11:27:25 AM: 5.2 is already installed.
11:27:25 AM: Using Swift version 5.2
11:27:25 AM: Started restoring cached node modules
11:27:25 AM: Finished restoring cached node modules
11:27:25 AM: Started restoring cached yarn cache
11:27:25 AM: Finished restoring cached yarn cache
11:27:25 AM: Installing NPM modules using Yarn version 1.17.0
11:27:26 AM: yarn install v1.17.0
11:27:26 AM: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
11:27:26 AM: [1/4] Resolving packages…
11:27:27 AM: success Already up-to-date.
11:27:27 AM: Done in 0.96s.
11:27:27 AM: NPM modules installed using Yarn
11:27:27 AM: Started restoring cached go cache
11:27:29 AM: Finished restoring cached go cache
11:27:29 AM: Installing Go version 1.12
11:27:29 AM: unset GOOS;
11:27:29 AM: unset GOARCH;
11:27:29 AM: export GOROOT=‘/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64’;
11:27:29 AM: export PATH=“/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64/bin:${PATH}”;
11:27:29 AM: go version >&2;
11:27:29 AM: export GIMME_ENV=‘/opt/buildhome/.gimme_cache/env/go1.12.linux.amd64.env’;
11:27:29 AM: go version go1.12 linux/amd64
11:27:29 AM: Installing missing commands
11:27:29 AM: Verify run directory
11:27:30 AM: ​
11:27:30 AM: ┌─────────────────────────────┐
11:27:30 AM: │ Netlify Build │
11:27:30 AM: └─────────────────────────────┘
11:27:30 AM: ​
11:27:30 AM: ❯ Version
11:27:30 AM: @netlify/build 3.0.1
11:27:30 AM: ​
11:27:30 AM: ❯ Flags
11:27:30 AM: deployId: 5f2310ef48072f000752ba66
11:27:30 AM: mode: buildbot
11:27:30 AM: ​
11:27:30 AM: ❯ Current directory
11:27:30 AM: /opt/build/repo
11:27:30 AM: ​
11:27:30 AM: ❯ Config file
11:27:30 AM: /opt/build/repo/netlify.toml
11:27:30 AM: ​
11:27:30 AM: ❯ Context
11:27:30 AM: production
11:27:30 AM: ​
11:27:30 AM: ┌───────────────────────────────────┐
11:27:30 AM: │ 1. Build command from Netlify app │
11:27:30 AM: └───────────────────────────────────┘
11:27:30 AM: ​
11:27:30 AM: $ gatsby build
11:27:33 AM: success open and validate gatsby-configs - 0.073s
11:27:36 AM: success load plugins - 3.465s
11:27:36 AM: plugin-netlify-cache: Restoring 1261 cached files for public directory with 0 already existing files.
11:27:39 AM: plugin-netlify-cache: Restoring 50 cached files for .cache directory with 1 already existing files.
11:27:43 AM: plugin-netlify-cache: Netlify cache restored
11:27:43 AM: success onPreInit - 6.974s
11:27:44 AM: success delete html and css files from previous builds - 0.265s
11:27:44 AM: success initialize cache - 0.864s
11:27:44 AM: success copy gatsby files - 0.046s
11:27:44 AM: warning gatsby-plugin-feed was initialized in gatsby-config.js without a title in a feed.
11:27:44 AM: This means that the plugin will use the default feed title, which may not match your use case.
11:27:44 AM: This behavior will be removed in the next major release of gatsby-plugin-feed.
11:27:44 AM: For more info, check out: Adding an RSS Feed | Gatsby
11:27:44 AM: success onPreBootstrap - 0.014s
11:27:45 AM: success createSchemaCustomization - 0.143s
11:27:49 AM: error Error processing Markdown file /opt/build/repo/content/blog/what-is-a-permanent-full-time-position/index.md:
11:27:49 AM: can not read a block mapping entry; a multiline key may not be an implicit key at line 7, column 1:
11:27:49 AM: ^
11:27:49 AM: not finished source and transform nodes - 4.126s
11:27:49 AM: ​
11:27:49 AM: ┌─────────────────────────────┐
11:27:49 AM: │ “build.command” failed │
11:27:49 AM: └─────────────────────────────┘
11:27:49 AM: ​
11:27:49 AM: Error message
11:27:49 AM: Command failed with exit code 1: gatsby build
11:27:49 AM: ​
11:27:49 AM: Error location
11:27:49 AM: In Build command from Netlify app:
11:27:49 AM: gatsby build
11:27:49 AM: ​
11:27:49 AM: Resolved config
11:27:49 AM: build:
11:27:49 AM: command: gatsby build
11:27:49 AM: commandOrigin: ui
11:27:49 AM: publish: /opt/build/repo/public
11:27:49 AM: headers:
11:27:49 AM: - for: /rss.xml
11:27:49 AM: values:
11:27:49 AM: Access-Control-Allow-Origin: ‘https://www.cobaltcounsel.com’
11:27:49 AM: Caching artifacts
11:27:49 AM: Started saving node modules
11:27:49 AM: Finished saving node modules
11:27:49 AM: Started saving build plugins
11:27:49 AM: Finished saving build plugins
11:27:49 AM: Started saving yarn cache
11:27:49 AM: Finished saving yarn cache
11:27:49 AM: Started saving pip cache
11:27:49 AM: Finished saving pip cache
11:27:49 AM: Started saving emacs cask dependencies
11:27:49 AM: Finished saving emacs cask dependencies
11:27:49 AM: Started saving maven dependencies
11:27:49 AM: Finished saving maven dependencies
11:27:49 AM: Started saving boot dependencies
11:27:49 AM: Finished saving boot dependencies
11:27:49 AM: Started saving go dependencies
11:27:51 AM: Finished saving go dependencies
11:27:51 AM: Error running command: Build script returned non-zero exit code: 1
11:27:51 AM: Failing build: Failed to build site
11:27:51 AM: Failed during stage ‘building site’: Build script returned non-zero exit code: 1
11:27:51 AM: Finished processing build request in 53.959212911s

[fool]

Have you checked out this build debugging guide, @KarinaFrappier ? It’s where we ask you to start with build problems - ensuring that it builds locally, and that you’ve tuned our versions of software like node and npm to use the same versions you use locally so that our builds more closely match your local builds:

[Support Guide] Debugging Netlify site builds

Last reviewed by Netlify Support - August, 2023 Note: This article is only about builds within Netlify’s Continuous Integration (CI) environment, as triggered from git commits or from incoming build webhooks. You can learn more in depth about how Netlify builds your site in this article about how our build bots build sites. Some background There are a fair number of reasons that a build could fail in Netlify’s CI environment, even if building works locally. Testing locally is always the place …

If you don’t find any success using the methods in that article, you’ll see at the end a few questions you can answer in this thread to show us what you’ve learned from debugging already, so we can build on that to give you what advice we can without becoming intimately familiar with your source code.