Nix NodeJS | 203 Members | |
| 58 Servers |
| Sender | Message | Time |
|---|---|---|
| 12 Nov 2023 | ||
| i'm saying if you want debug output you can get it like that | 16:11:31 | |
| it will not fix anything | 16:11:35 | |
| but this is a network issue so i imagine it'll go away in a bit anyway | 16:12:05 | |
| so you could just take a break and come back later 🤷🏻‍♀️ | 16:12:29 | |
In reply to @lily:lily.flowersI mean the non parallelism with just one core, that usually works for me | 16:13:51 | |
| how do you mean "usually works" exactly? | 16:14:11 | |
| we had a problem where network issues wouldn't properly be retried but that's been fixed on master for a few weeks and 23.05 for a few days | 16:14:40 | |
| if you think you're genuinely having issues with prefetch-npm-deps, can you please share your nixpkgs rev? | 16:16:00 | |
| (all of them if you have multiple nixpkgs in e.g. flake inputs, even if you don't think they should be used) | 16:16:25 | |
In reply to @lily:lily.flowersno I just experienced many little bugs over the years that were fixed and related to anything that has to do with nodejs and packaging. I guess it is just one of the weirdest things you can use on nix | 16:17:57 | |
| npm is very eager to do the wrong thing, so yeah unfortunately they were often there for a while | 16:49:38 | |
| turning off parallelism shouldn't ever help with anything but making the logs more coherent unless your internet link gets spooked by the concurrent connections to the same domain. but even then the retry backoff logic bacisally means they will eventually be tried one at a time if that causes problems noe | 16:50:59 | |
| * turning off parallelism shouldn't ever help with anything but making the logs more coherent unless your internet link gets spooked by the concurrent connections to the same domain. but even then the retry backoff logic bacisally means they will eventually be tried one at a time if that causes problems now | 16:51:02 | |
| * turning off parallelism shouldn't ever help with anything but making the logs more coherent unless your internet link gets spooked by the concurrent connections to the same domain. but even then the retry backoff logic basically means they will eventually be tried one at a time if that causes problems now | 16:51:17 | |
| 13 Nov 2023 | ||
| I try to build a small package.json with buildNpmPackage. I seem to deterministically (repeatdly) hit:
while | 16:57:15 | |
In reply to @keiichi:matrix.orgPrefetching that URL has nothing to do with npm trying to do something it shouldn't in the nix sandbox. Can you share the full lock and the package-lock.json file you are using? | 16:59:01 | |
(ENOTCACHED should really be renamed to ENPMDIDABADTHINGAGAIN) | 16:59:28 | |
| sure, where is the best place to upload those files ? | 17:02:43 | |
| i mean you could put them on a pastebin. or https://tmp.lily.flowers/ | 17:03:21 | |
In reply to @keiichi:matrix.org* Prefetching that URL has nothing to do with npm trying to do something it shouldn't in the nix sandbox. Can you share the full log and the package-lock.json file you are using? | 17:03:41 | |
| https://tmp.lily.flowers/package.json and the package-lock.json https://tmp.lily.flowers/wuhszr | 17:06:22 | |
| can you share full build log? | 17:08:41 | |
| i don't see anything wrong with this lockfile | 17:08:46 | |
| I build it with :
and a nixpkgs of 8ac5c1191b06206f8508595f0c17332b851240f0 | 17:10:01 | |
| let me regenerate the log | 17:10:50 | |
| i mean i've got it building on my end now | 17:13:18 | |
| oh it's happening during prune...?? | 17:14:22 | |
| what the hell | 17:14:26 | |
| (why does npm prune logic always have to be so horribly busted) | 17:15:37 | |
yes. I haven't tried dontNpmPrune = true yet, trying | 17:25:18 | |