Deploy details

2:21:58 AM: Build ready to start

2:22:13 AM: build-image version: e2302d7bf4e0ce66ded1ed62fd22903c51eee112 (focal)

2:22:13 AM: buildbot version: e2302d7bf4e0ce66ded1ed62fd22903c51eee112

2:22:13 AM: Fetching cached dependencies

2:22:13 AM: Failed to fetch cache, continuing with build

2:22:13 AM: Starting to prepare the repo for build

2:22:13 AM: No cached dependencies found. Cloning fresh repo

2:22:13 AM: git clone --filter=blob:none https://github.com/uclaacm/website

2:22:13 AM: Preparing Git Reference pull/739/head

2:22:16 AM: Custom build command detected. Proceeding with the specified command: 'npm run ofp; npm run thp; npm run gmp; npm run build'

2:22:17 AM: Starting to install dependencies

2:22:18 AM: mise python@3.13.2 install

2:22:18 AM: mise python@3.13.2 download cpython-3.13.2+20250212-x86_64-unknown-linux-gnu-install_only_stripped.tar.gz

2:22:18 AM: mise python@3.13.2 extract cpython-3.13.2+20250212-x86_64-unknown-linux-gnu-install_only_stripped.tar.gz

2:22:19 AM: mise python@3.13.2 python --version

2:22:19 AM: mise python@3.13.2 Python 3.13.2

2:22:19 AM: mise python@3.13.2 ✓ installed

2:22:19 AM: Python version set to 3.13

2:22:20 AM: Collecting pipenv

2:22:20 AM: Downloading pipenv-2024.4.1-py3-none-any.whl.metadata (17 kB)

2:22:20 AM: Collecting certifi (from pipenv)

2:22:20 AM: Downloading certifi-2025.1.31-py3-none-any.whl.metadata (2.5 kB)

2:22:20 AM: Collecting packaging>=22 (from pipenv)

2:22:20 AM: Downloading packaging-24.2-py3-none-any.whl.metadata (3.2 kB)

2:22:20 AM: Collecting setuptools>=67 (from pipenv)

2:22:20 AM: Downloading setuptools-75.8.0-py3-none-any.whl.metadata (6.7 kB)

2:22:20 AM: Collecting virtualenv>=20.24.2 (from pipenv)

2:22:20 AM: Downloading virtualenv-20.29.2-py3-none-any.whl.metadata (4.5 kB)

2:22:21 AM: Collecting distlib<1,>=0.3.7 (from virtualenv>=20.24.2->pipenv)

2:22:21 AM: Downloading distlib-0.3.9-py2.py3-none-any.whl.metadata (5.2 kB)

2:22:21 AM: Collecting filelock<4,>=3.12.2 (from virtualenv>=20.24.2->pipenv)

2:22:21 AM: Downloading filelock-3.17.0-py3-none-any.whl.metadata (2.9 kB)

2:22:21 AM: Collecting platformdirs<5,>=3.9.1 (from virtualenv>=20.24.2->pipenv)

2:22:21 AM: Downloading platformdirs-4.3.6-py3-none-any.whl.metadata (11 kB)

2:22:21 AM: Downloading pipenv-2024.4.1-py3-none-any.whl (3.0 MB)

2:22:21 AM: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.0/3.0 MB 56.4 MB/s eta 0:00:00

2:22:21 AM: Downloading packaging-24.2-py3-none-any.whl (65 kB)

2:22:21 AM: Downloading setuptools-75.8.0-py3-none-any.whl (1.2 MB)

2:22:21 AM: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 57.4 MB/s eta 0:00:00

2:22:21 AM: Downloading virtualenv-20.29.2-py3-none-any.whl (4.3 MB)

2:22:21 AM: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.3/4.3 MB 120.3 MB/s eta 0:00:00

2:22:21 AM: Downloading certifi-2025.1.31-py3-none-any.whl (166 kB)

2:22:21 AM: Downloading distlib-0.3.9-py2.py3-none-any.whl (468 kB)

2:22:21 AM: Downloading filelock-3.17.0-py3-none-any.whl (16 kB)

2:22:21 AM: Downloading platformdirs-4.3.6-py3-none-any.whl (18 kB)

2:22:21 AM: Installing collected packages: distlib, setuptools, platformdirs, packaging, filelock, certifi, virtualenv, pipenv

2:22:23 AM: Successfully installed certifi-2025.1.31 distlib-0.3.9 filelock-3.17.0 packaging-24.2 pipenv-2024.4.1 platformdirs-4.3.6 setuptools-75.8.0 virtualenv-20.29.2

2:22:23 AM: [notice] A new release of pip is available: 24.3.1 -> 25.0.1

2:22:23 AM: [notice] To update, run: pip install --upgrade pip

2:22:23 AM: Attempting Ruby version 2.7.1, read from environment

2:22:24 AM: Required ruby-2.7.1 is not installed - installing.

2:22:24 AM: Searching for binary rubies, this might take some time.

2:22:24 AM: Found remote file https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/20.04/x86_64/ruby-2.7.1.tar.bz2

2:22:24 AM: Checking requirements for ubuntu.

2:22:25 AM: Requirements installation successful.

2:22:25 AM: ruby-2.7.1 - #configure

2:22:25 AM: ruby-2.7.1 - #download

2:22:25 AM: ruby-2.7.1 - #validate archive

2:22:28 AM: ruby-2.7.1 - #extract

2:22:32 AM: ruby-2.7.1 - #validate binary

2:22:33 AM: ruby-2.7.1 - #setup

2:22:34 AM: ruby-2.7.1 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.7.1@global

2:22:35 AM: ruby-2.7.1 - #importing gemset /opt/buildhome/.rvm/gemsets/global.gems........................................

2:22:35 AM: ruby-2.7.1 - #generating global wrappers........

2:22:35 AM: ruby-2.7.1 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.7.1

2:22:35 AM: ruby-2.7.1 - #importing gemsetfile /opt/buildhome/.rvm/gemsets/default.gems evaluated to empty gem list

2:22:35 AM: ruby-2.7.1 - #generating default wrappers........

2:22:36 AM: Using /opt/buildhome/.rvm/gems/ruby-2.7.1

2:22:36 AM: Using Ruby version 2.7.1

2:22:37 AM: Started restoring cached go cache

2:22:37 AM: Finished restoring cached go cache

2:22:37 AM: Installing Go version 1.14.4 (requested 1.14.4)

2:22:42 AM: go version go1.14.4 linux/amd64

2:22:43 AM: Using PHP version 8.0

2:22:44 AM: Attempting Node.js version 'lts/iron' from .nvmrc

2:22:44 AM: Downloading and installing node v20.18.3...

2:22:44 AM: Downloading https://nodejs.org/dist/v20.18.3/node-v20.18.3-linux-x64.tar.xz...

2:22:45 AM: Computing checksum with sha256sum

2:22:45 AM: Checksums matched!

2:22:47 AM: Now using node v20.18.3 (npm v10.8.2)

2:22:47 AM: Enabling Node.js Corepack

2:22:47 AM: Started restoring cached build plugins

2:22:47 AM: Finished restoring cached build plugins

2:22:47 AM: Started restoring cached corepack dependencies

2:22:47 AM: Finished restoring cached corepack dependencies

2:22:47 AM: No npm workspaces detected

2:22:47 AM: Started restoring cached node modules

2:22:47 AM: Finished restoring cached node modules

2:22:47 AM: Installing npm packages using npm version 10.8.2

2:22:49 AM: npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

2:22:49 AM: npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported

2:22:50 AM: npm warn deprecated glob@7.1.7: Glob versions prior to v9 are no longer supported

2:22:52 AM: npm warn deprecated domexception@4.0.0: Use your platform's native DOMException instead
npm warn deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
npm warn deprecated @humanwhocodes/config-array@0.5.0: Use @eslint/config-array instead

2:22:52 AM: npm warn deprecated @humanwhocodes/object-schema@1.2.1: Use @eslint/object-schema instead

2:22:53 AM: npm warn deprecated eslint@7.32.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.

2:23:00 AM: added 774 packages, and audited 775 packages in 12s

2:23:00 AM: 174 packages are looking for funding

2:23:00 AM: run `npm fund` for details

2:23:00 AM: found 0 vulnerabilities

2:23:00 AM: npm packages installed

2:23:00 AM: Successfully installed dependencies

2:23:00 AM: Starting build script

2:23:02 AM: Detected 1 framework(s)

2:23:02 AM: "next" at version "15.1.7"

2:23:02 AM: Section completed: initializing

2:23:03 AM: Netlify Build

2:23:03 AM: ────────────────────────────────────────────────────────────────

2:23:03 AM: ​

2:23:03 AM: ❯ Version

2:23:03 AM: @netlify/build 29.59.1

2:23:03 AM: ​

2:23:03 AM: ❯ Flags

2:23:03 AM: accountId: 5f75eccd8af0700090155c32

2:23:03 AM: baseRelDir: true

2:23:03 AM: buildId: 67bd29453897a500082f403f

2:23:03 AM: deployId: 67bd29453897a500082f4041

2:23:03 AM: ​

2:23:03 AM: ❯ Current directory

2:23:03 AM: /opt/build/repo

2:23:03 AM: ​

2:23:03 AM: ❯ Config file

2:23:03 AM: /opt/build/repo/netlify.toml

2:23:03 AM: ​

2:23:03 AM: ❯ Context

2:23:03 AM: deploy-preview

2:23:03 AM: ​

2:23:03 AM: ❯ Installing plugins

2:23:03 AM: - @netlify/plugin-sitemap@0.8.1

2:23:03 AM: - netlify-plugin-cache-nextjs@1.4.0

2:23:08 AM: ​

2:23:08 AM: ❯ Using Next.js Runtime - v5.9.4

2:23:08 AM: ​

2:23:08 AM: ❯ Loading plugins

2:23:08 AM: - @netlify/plugin-sitemap@0.8.1 from Netlify app

2:23:08 AM: - netlify-plugin-cache-nextjs@1.4.0 from Netlify app

2:23:09 AM: No Next.js cache to restore

2:23:09 AM: No cache found for the .next folder at the location `.next/cache`

2:23:09 AM: ​

2:23:09 AM: build.command from netlify.toml

2:23:09 AM: ────────────────────────────────────────────────────────────────

2:23:09 AM: ​

2:23:09 AM: $ npm run ofp; npm run thp; npm run gmp; npm run build

2:23:10 AM: > acm-website@0.1.0 ofp

2:23:10 AM: > node scripts/officer-parser.mjs

2:23:11 AM: Output successfully saved to offoutput.json

2:23:11 AM: > acm-website@0.1.0 thp

2:23:11 AM: > node scripts/town-hall-generator.mjs

2:23:12 AM: Output successfully saved to townhall.json

2:23:12 AM: Output successfully saved to past-townhall.json

2:23:12 AM: > acm-website@0.1.0 gmp

2:23:12 AM: > node scripts/gm-generator.mjs

2:23:13 AM: Saved output: gmData.json

2:23:14 AM: Saved output: past-gm.json

2:23:14 AM: > acm-website@0.1.0 build

2:23:14 AM: > npm run ofp && npm run thp && npm run gmp && next build

2:23:14 AM: > acm-website@0.1.0 ofp

2:23:14 AM: > node scripts/officer-parser.mjs

2:23:15 AM: Output successfully saved to offoutput.json

2:23:15 AM: > acm-website@0.1.0 thp

2:23:15 AM: > node scripts/town-hall-generator.mjs

2:23:16 AM: Output successfully saved to townhall.json

2:23:16 AM: Output successfully saved to past-townhall.json

2:23:16 AM: > acm-website@0.1.0 gmp

2:23:16 AM: > node scripts/gm-generator.mjs

2:23:17 AM: Saved output: gmData.json

2:23:17 AM: Saved output: past-gm.json

2:23:18 AM: ⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache

2:23:18 AM: ▲ Next.js 15.1.7

2:23:18 AM: Linting and checking validity of types ...

2:23:19 AM:

2:23:19 AM: ./pages/gm/f21.js

2:23:19 AM: 218:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 226:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 231:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 239:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 247:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 255:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 260:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 265:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 279:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 287:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: ./pages/gm/w22.js

2:23:19 AM: 218:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 226:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 231:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 239:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 247:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 255:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 260:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 265:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 279:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: 287:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: ./pages/gm.js

2:23:19 AM: 7:10 Error: Parsing error: Identifier 'NextSeo' has already been declared

2:23:19 AM: ./components/Footer.js

2:23:19 AM: 119:27 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

2:23:19 AM: info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/app/api-reference/config/eslint#disabling-rules

2:23:19 AM: ​

2:23:19 AM: "build.command" failed

2:23:19 AM: ────────────────────────────────────────────────────────────────

2:23:19 AM: ​

2:23:19 AM: Error message

2:23:19 AM: Command failed with exit code 1: npm run ofp; npm run thp; npm run gmp; npm run build (https://ntl.fyi/exit-code-1)

2:23:19 AM: ​

2:23:19 AM: Error location

2:23:19 AM: In build.command from netlify.toml:

2:23:19 AM: npm run ofp; npm run thp; npm run gmp; npm run build

2:23:19 AM: ​

2:23:19 AM: Resolved config

2:23:19 AM: build:

2:23:19 AM: command: npm run ofp; npm run thp; npm run gmp; npm run build

2:23:19 AM: commandOrigin: config

2:23:19 AM: environment:

2:23:19 AM: - DIRECTORY_SPREADSHEET_ID

2:23:19 AM: - EVENTS_SPREADSHEET_ID

2:23:19 AM: - GM_SPREADSHEET_ID

2:23:19 AM: - NEXT_DISABLE_EDGE_IMAGES

2:23:19 AM: - REVIEW_ID

2:23:19 AM: - SERVICE_ACCOUNT

2:23:19 AM: - TOWNHALL_SPREADSHEET_ID

2:23:19 AM: - TZ

2:23:19 AM: publish: /opt/build/repo/.next

2:23:19 AM: publishOrigin: config

2:23:19 AM: plugins:

2:23:19 AM: - inputs: {}

2:23:19 AM: origin: config

2:23:19 AM: package: '@netlify/plugin-nextjs'

2:23:19 AM: - inputs: {}

2:23:19 AM: origin: ui

2:23:19 AM: package: '@netlify/plugin-sitemap'

2:23:19 AM: - inputs: {}

2:23:19 AM: origin: ui

2:23:19 AM: package: netlify-plugin-cache-nextjs

2:23:20 AM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)

2:23:20 AM: Build failed due to a user error: Build script returned non-zero exit code: 2

2:23:20 AM: Failing build: Failed to build site

2:23:20 AM: Finished processing build request in 1m7.356s