Nix NodeJS | 195 Members | |
| 58 Servers |
| Sender | Message | Time |
|---|---|---|
| 28 Nov 2024 | ||
| Is there something I can try to help him? | 13:50:19 | |
In reply to@drupol:matrix.orgIf you still need help, it just means they OOMd while running it: 3: 0xe7d2a4 v8::internal::V8::FatalProcessOutOfMemoryIt should show up better on the in logs before that with something like: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory | 15:44:32 | |
If you still need help, it just means they OOMd while running it:3: 0xe7d2a4 v8::internal::V8::FatalProcessOutOfMemoryIt should show up better in logs before that with something like: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory | 15:44:51 | |
<del>If you still need help, it just means they OOMd while running it:3: 0xe7d2a4 v8::internal::V8::FatalProcessOutOfMemoryIt should show up better in logs before that with something like: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory</del>Run it myself and node needs more than default memory for whatever open-webui is doing.With env.NODE_OPTIONS = "--max-old-space-size=8192"; it seems to build. | 16:14:05 | |
~If you still need help, it just means they OOMd while running it:3: 0xe7d2a4 v8::internal::V8::FatalProcessOutOfMemoryIt should show up better in logs before that with something like: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory~Run it myself and node needs more than default memory for whatever open-webui is doing.With env.NODE_OPTIONS = "--max-old-space-size=8192"; it seems to build. | 16:14:34 | |
| Run it myself and node needs more than default memory for whatever open-webui is doing.With env.NODE_OPTIONS = "--max-old-space-size=8192"; it seems to build. | 16:14:54 | |
| OK | 16:22:39 | |
| I will let him know | 16:22:44 | |
| Thanks for the help :) I'll keep you posted | 16:22:53 | |
| ghpzin: Do you think I should submit a PR to fix this upstream? | 16:23:33 | |
As in nixpkgs or open-webui ?open-webui preferably would look into why it happens, but afaik for most of these problems people just tell to add --max-old-space-size with some high number and if it works - it works. | 16:27:40 | |
| Pretty sure in nixpkgs there are a few of those too. | 16:28:15 | |
Pretty sure in nixpkgs there are a few of those too, that just have --max-old-space-size with some higher number.If you want to just temp override your flake, patch: https://gist.github.com/ghpzin/2c953016de3f744648ad55fcb1cc7ad6 (thought it couples to frontend with version/src, because it is not exposed from nixpkgs package) | 16:29:47 | |
Pretty sure in nixpkgs there are a few of those too, that just have --max-old-space-size with some higher number.If you want to just temp override your flake, patch: https://gist.github.com/ghpzin/2c953016de3f744648ad55fcb1cc7ad6 (I copy-pasted frontend with version/src, but there is probably a better way to get it from nixpkgs package) | 16:31:26 | |
Pretty sure in nixpkgs there are a few of those too, that just have --max-old-space-size with some higher number:3 according to search: https://github.com/search?q=repo%3ANixOS%2Fnixpkgs%20max-old-space-size&type=code If you want to just temp override your flake, patch: https://gist.github.com/ghpzin/2c953016de3f744648ad55fcb1cc7ad6 (I copy-pasted frontend with version/src, but there is probably a better way to get it from nixpkgs package) | 16:32:44 | |
| @Pol As in nixpkgs or open-webui ?open-webui preferably would look into why it happens, but afaik for most of these problems people just tell to add --max-old-space-size with some high number and if it works - it works. | 16:35:08 | |
Pretty sure in nixpkgs there are a few of those too, that just have --max-old-space-size with some higher number - 3 according to search:https://github.com/search?q=repo%3ANixOS%2Fnixpkgs%20max-old-space-size&type=code If you want to just temp override your flake, patch: https://gist.github.com/ghpzin/2c953016de3f744648ad55fcb1cc7ad6 (I copy-pasted frontend with version/src, but there is probably a better way to get it from nixpkgs package) | 16:35:41 | |
| Thank you :) | 16:36:21 | |
Going to submit the patch to nixpkgs | 16:36:27 | |
| If you can validate it: https://github.com/NixOS/nixpkgs/pull/359891 | 16:42:14 | |
| @Pol : Tried and commented. Surprisingly previous version 0.4.4 from nixos-unstable builds fine either way, so upstream probably added something between those versions that is heavy enough to trip over memory limits. | 17:20:30 | |
| Thank you :) | 17:21:20 | |
| Merging this now | 17:21:26 | |
| 29 Nov 2024 | ||
| 01:11:44 | ||
| 01:12:00 | ||
| 18:30:07 | ||
| 2 Dec 2024 | ||
| 19:59:08 | ||
| 3 Dec 2024 | ||
trying to package something that needs me to patch its yarn.lock. How can I pass that change through to fetchYarnDeps so that the dependencies fetch properly? | 19:33:15 | |
I've tried making a patch and passing in patches, as well as a custom postPatch, and neither worked | 19:34:10 | |
also, I'm going to make a PR dropping the nodePackages.webpack package, as nothing in-tree uses it, and if you're making a node package, it should be pulled from your lockfile via your package manager anyways. webpack-dev-server and webpack-cli are fine to keep, though. | 23:48:29 | |