SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Grist update fails #458

New Issue
Closed
opened 2025-11-20 04:48:52 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 04:48:52 -05:00
Owner
Copy Link

Originally created by @wms8688 on GitHub (Feb 2, 2025).

Originally assigned to: @MickLesk on GitHub.

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Grist

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/grist.sh)"

📝 Provide a clear and concise description of the issue.

Update fails with the following error: [ERROR] in line 51: exit code 0: while executing command yarn run build:prod > /dev/null 2>&1

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

run bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/grist.sh)"

❌ Paste the full error output (if available).

There is no Advanced or verbose mode that I can find so I changed directory to /opt/grist and ran the failed command, below is the output

root@grist:/opt/grist# yarn run build:prod
yarn run v1.22.22
$ buildtools/build.sh
No extra app directory found

  • node buildtools/sanitize_translations.js
  • tsc --build
  • buildtools/update_type_info.sh app
  • webpack --config buildtools/webpack.config.js --mode production

<--- Last few GCs --->

[3844:0x2ec68060] 88264 ms: Scavenge 997.8 (1039.5) -> 992.2 (1040.0) MB, 6.98 / 0.00 ms (average mu = 0.223, current mu = 0.203) allocation failure;
[3844:0x2ec68060] 88278 ms: Scavenge 998.9 (1040.0) -> 993.2 (1041.2) MB, 10.49 / 0.00 ms (average mu = 0.223, current mu = 0.203) allocation failure;
[3844:0x2ec68060] 89365 ms: Mark-Compact 1000.1 (1041.2) -> 993.4 (1043.0) MB, 1083.31 / 0.00 ms (average mu = 0.168, current mu = 0.110) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0xb8d0a3 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [webpack]
2: 0xf062e0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [webpack]
3: 0xf065c7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [webpack]
4: 0x1118165 [webpack]
5: 0x11186f4 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [webpack]
6: 0x112f5e4 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [webpack]
7: 0x112fdfc v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [webpack]
8: 0x1106101 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
9: 0x1107295 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
10: 0x10e48e6 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [webpack]
11: 0x1540716 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [webpack]
12: 0x1979ef6 [webpack]
buildtools/build.sh: line 24: 3844 Aborted webpack --config $WEBPACK_CONFIG --mode production
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

🖼️ Additional context (optional).

No response

Originally created by @wms8688 on GitHub (Feb 2, 2025). Originally assigned to: @MickLesk on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Grist ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/grist.sh)" ### 📝 Provide a clear and concise description of the issue. Update fails with the following error: [ERROR] in line 51: exit code 0: while executing command yarn run build:prod > /dev/null 2>&1 ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. run bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/grist.sh)" ### ❌ Paste the full error output (if available). There is no Advanced or verbose mode that I can find so I changed directory to /opt/grist and ran the failed command, below is the output root@grist:/opt/grist# yarn run build:prod yarn run v1.22.22 $ buildtools/build.sh No extra app directory found + node buildtools/sanitize_translations.js + tsc --build + buildtools/update_type_info.sh app + webpack --config buildtools/webpack.config.js --mode production <--- Last few GCs ---> [3844:0x2ec68060] 88264 ms: Scavenge 997.8 (1039.5) -> 992.2 (1040.0) MB, 6.98 / 0.00 ms (average mu = 0.223, current mu = 0.203) allocation failure; [3844:0x2ec68060] 88278 ms: Scavenge 998.9 (1040.0) -> 993.2 (1041.2) MB, 10.49 / 0.00 ms (average mu = 0.223, current mu = 0.203) allocation failure; [3844:0x2ec68060] 89365 ms: Mark-Compact 1000.1 (1041.2) -> 993.4 (1043.0) MB, 1083.31 / 0.00 ms (average mu = 0.168, current mu = 0.110) allocation failure; scavenge might not succeed <--- JS stacktrace ---> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory ----- Native stack trace ----- 1: 0xb8d0a3 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [webpack] 2: 0xf062e0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [webpack] 3: 0xf065c7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [webpack] 4: 0x1118165 [webpack] 5: 0x11186f4 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [webpack] 6: 0x112f5e4 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [webpack] 7: 0x112fdfc v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [webpack] 8: 0x1106101 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack] 9: 0x1107295 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack] 10: 0x10e48e6 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [webpack] 11: 0x1540716 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [webpack] 12: 0x1979ef6 [webpack] buildtools/build.sh: line 24: 3844 Aborted webpack --config $WEBPACK_CONFIG --mode production error Command failed with exit code 134. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. ### 🖼️ Additional context (optional). _No response_
saavagebueno commented 2025-11-20 04:48:53 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 2, 2025):

Java Heap Space. Can you run in Advanced and Double RAM / Core? Please give Feedback after this

@MickLesk commented on GitHub (Feb 2, 2025): Java Heap Space. Can you run in Advanced and Double RAM / Core? Please give Feedback after this
saavagebueno commented 2025-11-20 04:48:53 -05:00
Author
Owner
Copy Link

@wms8688 commented on GitHub (Feb 2, 2025):

Doubling the RAM and cores allows the update to complete successfully

@wms8688 commented on GitHub (Feb 2, 2025): Doubling the RAM and cores allows the update to complete successfully
saavagebueno commented 2025-11-20 04:48:53 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 2, 2025):

Good, i fix it tomorrow 👍

@MickLesk commented on GitHub (Feb 2, 2025): Good, i fix it tomorrow 👍
saavagebueno commented 2025-11-20 04:48:53 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 3, 2025):

done

@MickLesk commented on GitHub (Feb 3, 2025): done
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#458
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?