Skip to content
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.

[Bug]: deployment failing on various cloud providers #625

Closed
TWINGSISTER opened this issue Aug 6, 2022 · 7 comments
Closed

[Bug]: deployment failing on various cloud providers #625

TWINGSISTER opened this issue Aug 6, 2022 · 7 comments
Assignees
@win11bot
Labels
bug Something isn't working

Comments

@TWINGSISTER
Copy link

What happened?

Deploy works fine then vite fails. Running on free dynos in Heroku.

2022-08-06T08:39:38.347888+00:00 app[web.1]:
2022-08-06T08:39:38.347900+00:00 app[web.1]: > [email protected] start
2022-08-06T08:39:38.347901+00:00 app[web.1]: > vite
2022-08-06T08:39:38.347901+00:00 app[web.1]:
2022-08-06T08:39:38.354156+00:00 app[web.1]: sh: 1: vite: not found
2022-08-06T08:39:38.484340+00:00 heroku[web.1]: Process exited with status 127
2022-08-06T08:39:38.700683+00:00 heroku[web.1]: State changed from starting to crashed
2022-08-06T08:41:19.671013+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=twingsisterw11.herokuapp.com request_id=53f939a4-7e3d-42d9-b273-cb86f59d7115 fwd="79.51.193.210" dyno= connect= service= status=503 bytes= protocol=https
2022-08-06T08:41:20.204311+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=twingsisterw11.herokuapp.com request_id=944eb4f1-9607-49e2-8bb6-63f2e85dc096 fwd="79.51.193.210" dyno= connect= service= status=503 bytes= protocol=https
2022-08-06T08:42:30.690935+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=twingsisterw11.herokuapp.com request_id=42d49b14-d442-4b36-a6b0-fb795053aeac fwd="79.51.193.210" dyno= connect= service= status=503 bytes= protocol=https
2022-08-06T08:48:24.478376+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=twingsisterw11.herokuapp.com request_id=86ed2e85-0786-4dca-b7ce-ba70e996b6fb fwd="79.51.193.210" dyno= connect= service= status=503 bytes= protocol=https

To reproduce the behavior?

reproduce!

What browser are you seeing the problem on?

Firefox
@TWINGSISTER TWINGSISTER added the bug Something isn't working label Aug 6, 2022
@win11bot
Copy link
Collaborator

win11bot commented Aug 6, 2022

Hey, thank you for creating an issue. We will normally respond within 24 hours.

@TWINGSISTER
Copy link
Author

Fails on railway, too, during build

=========================
Using Detected Dockerfile
=========================
#1 [internal] load build definition from Dockerfile

#1 sha256:7f88cb51e95e2c56315400d13cca68c88c827740b1ad26af82a4b3a9aacb6b78
#1 transferring dockerfile: 683B done

#1 DONE 0.5s

#2 [internal] load .dockerignore
#2 sha256:34a6bb64a2c5daea0c2ead36d1be05dc194ba6158f043b12f3ea09b4a0055f6d
#2 transferring context: 48B done
#2 DONE 0.6s

#3 [internal] load metadata for docker.io/library/node:14-alpine3.14
#3 sha256:67820c123a43010c00418d79c7a98367573500fc43695d0f8bbe15468138c4d4

#3 DONE 0.7s

#4 [1/5] FROM docker.io/library/node:14-alpine3.14@sha256:f6bd262df57e5cb454ace4f0b2c58b69727bf2ae38d89a5e0a1658d839d7c618
#4 sha256:ccc99e07dd7ccb757af74cb21dea33b9a0e1a4598c200045f2e6194dcd396815
#4 DONE 0.0s

#5 [2/5] WORKDIR /usr/src/windows11/

#5 sha256:2520e0bbfcfd63723e5042b77574a038a83dabb7fd74d5cbb8a1a2e1a98380c6
#5 CACHED

#6 [3/5] RUN npm install -g serve
#6 sha256:18b55ff5ec8660e6b67685064c49a24c1d24230a2c82d3f693ba634fda2ae092
#6 CACHED

#7 [4/5] RUN wget https://github.com/blueedgetechno/win11React/archive/refs/heads/gh-pages.zip
#7 sha256:231e3c91e480f00b0cca303b5a82cb1ace619023ff20c7e6c8127c56e5028e75

#7 0.464 Connecting to github.com (192.30.255.113:443)

#7 0.687 Connecting to codeload.github.com (192.30.255.121:443)

#7 0.853 wget: server returned error: HTTP/1.1 404 Not Found

#7 ERROR: executor failed running [/bin/sh -c wget https://github.com/blueedgetechno/win11React/archive/refs/heads/gh-pages.zip]: exit code: 1

[4/5] RUN wget https://github.com/blueedgetechno/win11React/archive/refs/heads/gh-pages.zip:

executor failed running [/bin/sh -c wget https://github.com/blueedgetechno/win11React/archive/refs/heads/gh-pages.zip]: exit code: 1

@TWINGSISTER
Copy link
Author

and also netlify
1:59:12 PM: Build ready to start
1:59:17 PM: build-image version: d7b3dbfb0846505993c9a131894d1858074c90b4 (focal)
1:59:17 PM: build-image tag: v4.10.1
1:59:17 PM: buildbot version: fe6512288e75c8fa5aadaebb51ed1f96e9314fd4
1:59:18 PM: Fetching cached dependencies
1:59:18 PM: Failed to fetch cache, continuing with build
1:59:18 PM: Starting to prepare the repo for build
1:59:18 PM: No cached dependencies found. Cloning fresh repo
1:59:18 PM: git clone https://github.com/blueedgetechno/win11React
1:59:20 PM: Preparing Git Reference refs/heads/master
1:59:20 PM: Parsing package.json dependencies
1:59:21 PM: Starting build script
1:59:21 PM: Installing dependencies
1:59:21 PM: Python version set to 2.7
1:59:21 PM: v16.16.0 is already installed.
1:59:21 PM: Now using node v16.16.0 (npm v8.11.0)
1:59:21 PM: Started restoring cached build plugins
1:59:21 PM: Finished restoring cached build plugins
1:59:22 PM: Attempting ruby version 2.7.2, read from environment
1:59:22 PM: Using ruby version 2.7.2
1:59:22 PM: Using PHP version 8.0
1:59:23 PM: No npm workspaces detected
1:59:23 PM: Started restoring cached node modules
1:59:23 PM: Finished restoring cached node modules
1:59:23 PM: Installing NPM modules using NPM version 8.11.0
1:59:23 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
1:59:23 PM: npm WARN config location in the cache, and they are managed by
1:59:23 PM: npm WARN config cacache.
1:59:23 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
1:59:23 PM: npm WARN config location in the cache, and they are managed by
1:59:23 PM: npm WARN config cacache.
1:59:31 PM: npm WARN deprecated [email protected]: replaced by i18next-http-backend
1:59:35 PM: npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
1:59:38 PM: added 756 packages, and audited 757 packages in 14s
1:59:38 PM: 105 packages are looking for funding
1:59:38 PM: run npm fund for details
1:59:38 PM: found 0 vulnerabilities
1:59:38 PM: NPM modules installed
1:59:38 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
1:59:38 PM: npm WARN config location in the cache, and they are managed by
1:59:38 PM: npm WARN config cacache.
1:59:38 PM: Started restoring cached go cache
1:59:38 PM: Finished restoring cached go cache
1:59:38 PM: Installing Go version 1.17 (requested 1.17)
1:59:42 PM: unset GOOS;
1:59:42 PM: unset GOARCH;
1:59:42 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.17.linux.amd64';
1:59:42 PM: export PATH="/opt/buildhome/.gimme/versions/go1.17.linux.amd64/bin:${PATH}";
1:59:42 PM: go version >&2;
1:59:42 PM: export GIMME_ENV="/opt/buildhome/.gimme/env/go1.17.linux.amd64.env"
1:59:42 PM: go version go1.17 linux/amd64
1:59:42 PM: Installing missing commands
1:59:42 PM: Verify run directory
1:59:43 PM: ​
1:59:43 PM: ────────────────────────────────────────────────────────────────
1:59:43 PM: Netlify Build
1:59:43 PM: ────────────────────────────────────────────────────────────────
1:59:43 PM: ​
1:59:43 PM: ❯ Version
1:59:43 PM: @netlify/build 27.9.1
1:59:43 PM: ​
1:59:43 PM: ❯ Flags
1:59:43 PM: baseRelDir: true
1:59:43 PM: buildId: 62ee579045349f43f83a3da4
1:59:43 PM: deployId: 62ee579045349f43f83a3da6
1:59:43 PM: systemLogFile: 3
1:59:43 PM: ​
1:59:43 PM: ❯ Current directory
1:59:43 PM: /opt/build/repo
1:59:43 PM: ​
1:59:43 PM: ❯ Config file
1:59:43 PM: No config file was defined: using default values.
1:59:43 PM: ​
1:59:43 PM: ❯ Context
1:59:43 PM: production
1:59:43 PM: ​
1:59:43 PM: ────────────────────────────────────────────────────────────────
1:59:43 PM: 1. Build command from Netlify app
1:59:43 PM: ────────────────────────────────────────────────────────────────
1:59:43 PM: ​
1:59:43 PM: $ npm run build
1:59:43 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
1:59:43 PM: npm WARN config location in the cache, and they are managed by
1:59:43 PM: npm WARN config cacache.
1:59:43 PM: > [email protected] build
1:59:43 PM: > vite build
1:59:44 PM: vite v3.0.4 building for production...
1:59:44 PM: transforming...
1:59:47 PM: Module level directives cause errors when bundled, 'use babel' was ignored.
1:59:47 PM: Module level directives cause errors when bundled, 'use babel' was ignored.
1:59:49 PM: Use of eval is strongly discouraged, as it poses security risks and may cause issues with minification
1:59:50 PM: ✓ 490 modules transformed.
1:59:50 PM: rendering chunks...
1:59:50 PM: build/assets/spotify.2699cb74.woff2 54.23 KiB
1:59:50 PM: build/assets/SettingsIcons.166d2107.woff2 60.55 KiB
1:59:50 PM: build/assets/server.f30e785e.jpg 21.41 KiB
1:59:50 PM: build/assets/spotify.e2d45b27.ttf 184.50 KiB
1:59:50 PM: build/index.html 1.78 KiB
1:59:50 PM: build/manifest.webmanifest 0.14 KiB
1:59:50 PM: build/registerSW.js 0.13 KiB
1:59:50 PM: build/assets/index.a7cbf2af.css 93.90 KiB / gzip: 18.56 KiB
1:59:51 PM: build/assets/index.3b758049.js 2502.79 KiB / gzip: 741.65 KiB
1:59:51 PM:
1:59:51 PM: (!) Some chunks are larger than 500 KiB after minification. Consider:
1:59:51 PM: - Using dynamic import() to code-split the application
1:59:51 PM: - Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/guide/en/#outputmanualchunks
1:59:51 PM: - Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
1:59:53 PM: PWA v0.12.3
1:59:53 PM: mode generateSW
1:59:53 PM: precache 13 entries (343.60 KiB)
1:59:53 PM: files generated
1:59:53 PM: build/sw.js
1:59:53 PM: build/workbox-3ea082d2.js
1:59:53 PM: warnings
1:59:53 PM: assets/index.3b758049.js is 2.56 MB, and won't be precached. Configure maximumFileSizeToCacheInBytes to change this limit.
1:59:53 PM: ​
1:59:53 PM: (build.command completed in 9.7s)
1:59:53 PM: ​
1:59:53 PM: ────────────────────────────────────────────────────────────────
1:59:53 PM: 2. Deploy site
1:59:53 PM: ────────────────────────────────────────────────────────────────
1:59:53 PM: ​
1:59:53 PM: ​
1:59:53 PM: ────────────────────────────────────────────────────────────────
1:59:53 PM: Configuration error
1:59:53 PM: ────────────────────────────────────────────────────────────────
1:59:53 PM: ​
1:59:53 PM: Error message
1:59:53 PM: Deploy did not succeed: Deploy directory 'dist' does not exist
1:59:53 PM: ​
1:59:53 PM: Resolved config
1:59:53 PM: build:
1:59:53 PM: command: npm run build
1:59:53 PM: commandOrigin: ui
1:59:53 PM: publish: /opt/build/repo/dist
1:59:53 PM: publishOrigin: ui
1:59:53 PM: Caching artifacts
1:59:53 PM: Started saving node modules
1:59:53 PM: Finished saving node modules
1:59:53 PM: Started saving build plugins
1:59:53 PM: Finished saving build plugins
1:59:53 PM: Started saving pip cache
1:59:53 PM: Finished saving pip cache
1:59:53 PM: Started saving emacs cask dependencies
1:59:53 PM: Finished saving emacs cask dependencies
1:59:53 PM: Started saving maven dependencies
1:59:53 PM: Finished saving maven dependencies
1:59:53 PM: Started saving boot dependencies
1:59:53 PM: Finished saving boot dependencies
1:59:53 PM: Started saving rust rustup cache
1:59:53 PM: Finished saving rust rustup cache
1:59:53 PM: Started saving go dependencies
1:59:53 PM: Finished saving go dependencies
1:59:54 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
1:59:54 PM: Creating deploy upload records
1:59:54 PM: Failing build: Failed to build site
1:59:54 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
1:59:54 PM: Finished processing build request in 36.892049447s

@TWINGSISTER
Copy link
Author

and also Vercel
[14:04:47.880] Cloning github.com/TWINGSISTER/winreact16 (Branch: main, Commit: e973349)
[14:04:48.759] Cloning completed: 878.295ms
[14:04:49.153] Installing build runtime...
[14:04:51.651] Build runtime installed: 2.498s
[14:04:52.154] Looking up build cache...
[14:04:52.390] Build Cache not found
[14:04:52.624] Detected pnpm-lock.yaml generated by pnpm 7...
[14:04:52.646] Installing dependencies...
[14:04:53.200] Lockfile is up-to-date, resolution step is skipped
[14:04:53.204]  ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up-to-date with package.json
[14:04:53.204]
[14:04:53.205] Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"
[14:04:53.214] Error: Command "pnpm install" exited with 1

@yashash-pugalia
Copy link
Collaborator

yashash-pugalia commented Aug 6, 2022 •
edited
Loading

#7 ERROR: executor failed running [/bin/sh -c wget https://github.com/blueedgetechno/win11React/archive/refs/heads/gh-pages.zip]: exit code: 1

for railway it is trying to get the gh-pages branch which no longer exists

[14:04:53.205] Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"

for vercel you need to set CI as false

1:59:53 PM: Deploy did not succeed: Deploy directory 'dist' does not exist

for netlify it is trying to get the dist folder after building instead of build folder where the files are actually stored after the build.

@yashash-pugalia yashash-pugalia changed the title [Bug]: Heroku deploy button [Bug]: deployment failing on various cloud providers Aug 6, 2022
@TWINGSISTER
Copy link
Author

Thanks for your prompt reply!
Sorry no experience in DevOps, Seemed to be this to be done, yet...
image
still...
[15:53:51.997] Cloning github.com/TWINGSISTER/reactw11 (Branch: main, Commit: e205f62)
[15:53:52.852] Cloning completed: 854.594ms
[15:53:53.016] Installing build runtime...
[15:53:54.965] Build runtime installed: 1.948s
[15:53:55.756] No Build Cache available
[15:53:56.035] Detected pnpm-lock.yaml generated by pnpm 7...
[15:53:56.055] Installing dependencies...
[15:53:56.588] Lockfile is up-to-date, resolution step is skipped
[15:53:56.591]  ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up-to-date with package.json
[15:53:56.591]
[15:53:56.591] Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"
[15:53:56.601] Error: Command "pnpm install" exited with 1

@yashash-pugalia
Copy link
Collaborator

yashash-pugalia commented Aug 7, 2022 •
edited
Loading

image

for netlify i used these settings and it worked fine https://win11react-test.netlify.app see for yourself.

had to change build command to npm run ghbuild instead of npm run build by default & changed publish directory to build instead of dist .

similarly for others too few settings have to be tweaked to get them to work.

Hopefully this solves your issue

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@win11bot win11bot

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@TWINGSISTER @yashash-pugalia @win11bot