Conversation

Notices

1. Embed this notice
   Poppy Farbird (Pen Name) (limepeep@kitty.social)'s status on Thursday, 22-Feb-2024 11:55:26 JST Poppy Farbird (Pen Name)

   Uhhhh, a different error message popped up this time. Didn't really need to just keep waiting after all. Not sure what's happening, still.misskey@Poppyweb:~/misskey$ NODE_ENV=production pnpm run build > misskey@2024.2.0 build /home/misskey/misskey > pnpm build-pre && pnpm -r build && pnpm build-assets > misskey@2024.2.0 build-pre /home/misskey/misskey > node ./scripts/build-pre.js Scope: 7 of 8 workspace projects packages/misskey-bubble-game build$ node ./build.js └─ Done in 569ms packages/misskey-js build$ npm run ts │ > misskey-js@2024.2.0 ts │ > npm run ts-esm && npm run ts-dts │ > misskey-js@2024.2.0 ts-esm │ > tsc --outDir built/esm │ > misskey-js@2024.2.0 ts-dts │ > tsc --outDir built/dts --declaration true --emitDeclarationOnly true --declarationMap t… └─ Done in 21.6s packages/misskey-reversi build$ node ./build.js └─ Done in 560ms packages/backend build$ swc src -d built -D │ Successfully compiled: 800 files, copied 27 files with swc (50.95ms) └─ Done in 3.8s packages/frontend build$ vite build │ vite v5.1.0 building for production... │ transforming... │ ../misskey-bubble-game/built/esm/index.js (1:30) "Mono" is not exported by "../misskey-bu… │ │ [870913:0x61df630] 90671 ms: Mark-Compact 973.2 (1003.9) -> 969.1 (1003.9) MB, 2422.47… │ [870913:0x61df630] 93259 ms: Mark-Compact 973.2 (1003.9) -> 969.1 (1003.9) MB, 2395.75… │ │ FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript hea… │ ----- Native stack trace ----- │ 1: 0xcc0a72 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node] │ 2: 0x1054530 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDet… │ 3: 0x1054817 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char cons… │ 4: 0x1273a55 [node] │ 5: 0x1273f2e [node] │ 6: 0x1289156 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector… │ 7: 0x1289c79 [node] │ 8: 0x128a288 [node] │ 9: 0x19d9cb1 [node] │ Aborted └─ Failed in 1m 36.1s at /home/misskey/misskey/packages/frontend packages/sw build$ node build.js │ (node:870918) ExperimentalWarning: Importing JSON modules is an experimental feature and … │ (Use `node --trace-warnings ...` to show where the warning was created) │ Starting SW building... │ done └─ Done in 3.4s /home/misskey/misskey/packages/frontend:  ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  frontend@ build: `vite build` Exit status 134  ELIFECYCLE  Command failed with exit code 1.

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Thursday, 22-Feb-2024 11:55:25 JST iced depresso

     in reply to
     @limepeep > │ FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript hea…
     
     ran out of memory.
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Thursday, 22-Feb-2024 12:00:35 JST iced depresso

     in reply to
     @limepeep i don't know where you run your services but if you are dead set on doing your own builds and your local boxes are unsuitable, places like docean and vultr will rent you a large VPS on a by-the-minute charge.
     
     you might be able to do swap shenanigans to fake having enough memory, but it will be quite slow and still might fail
   • Embed this notice
     Poppy Farbird (Pen Name) (limepeep@kitty.social)'s status on Thursday, 22-Feb-2024 12:00:37 JST Poppy Farbird (Pen Name)

     in reply to

     • iced depresso

     @icedquinn@blob.cat Yep, that's the most common solution I found when searching up "pnpm run build fails" in general. Not sure if I've written it wrong, though, or if my $10/mo. VPS is still weaker than a Pentium II processor. Maybe I should just install the Misskey docker package or Akkoma, then.misskey@Poppyweb:~/misskey$ NODE_ENV=production pnpm run build NODE_OPTIONS=--max-old-space-size=4096 > misskey@2024.2.0 build /home/misskey/misskey > pnpm build-pre && pnpm -r build && pnpm build-assets "NODE_OPTIONS=--max-old-space-size=4096" > misskey@2024.2.0 build-pre /home/misskey/misskey > node ./scripts/build-pre.js Scope: 7 of 8 workspace projects packages/misskey-bubble-game build$ node ./build.js └─ Done in 501ms packages/misskey-js build$ npm run ts │ > misskey-js@2024.2.0 ts │ > npm run ts-esm && npm run ts-dts │ > misskey-js@2024.2.0 ts-esm │ > tsc --outDir built/esm │ > misskey-js@2024.2.0 ts-dts │ > tsc --outDir built/dts --declaration true --emitDeclarationOnly true --declarationMap t… └─ Done in 21.5s packages/misskey-reversi build$ node ./build.js └─ Done in 510ms packages/backend build$ swc src -d built -D │ Successfully compiled: 800 files, copied 27 files with swc (976.5ms) └─ Done in 3.5s packages/frontend build$ vite build │ vite v5.1.0 building for production... │ transforming... │ ../misskey-bubble-game/built/esm/index.js (1:30) "Mono" is not exported by "../misskey-bu… │ │ [871856:0x5f10630] 86143 ms: Mark-Compact 973.5 (1002.9) -> 969.2 (1002.7) MB, 2305.62… │ [871856:0x5f10630] 88703 ms: Mark-Compact 973.2 (1002.7) -> 969.2 (1002.9) MB, 2200.60… │ │ FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript hea… │ ----- Native stack trace ----- │ 1: 0xcc0a72 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node] │ 2: 0x1054530 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDet… │ 3: 0x1054817 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char cons… │ 4: 0x1273a55 [node] │ 5: 0x1273f2e [node] │ 6: 0x1289156 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector… │ 7: 0x1289c79 [node] │ 8: 0x128a288 [node] │ 9: 0x19d9cb1 [node] │ Aborted └─ Failed in 1m 31.5s at /home/misskey/misskey/packages/frontend packages/sw build$ node build.js │ (node:871859) ExperimentalWarning: Importing JSON modules is an experimental feature and … │ (Use `node --trace-warnings ...` to show where the warning was created) │ Starting SW building... │ done └─ Done in 3.3s /home/misskey/misskey/packages/frontend:  ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  frontend@ build: `vite build` Exit status 134  ELIFECYCLE  Command failed with exit code 1.

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Thursday, 22-Feb-2024 12:01:17 JST iced depresso

     in reply to

     • iced depresso
     @limepeep a tip: any time you see OOMKiller, thats the "out of memory killer," a subsystem of linux that yeets a process when its exhausted all of the memory.