Nix NodeJS - Public Room Timeline

	Nix NodeJS	210 Members
		61 Servers

Load older messages

Sender	Message	Time
6 Oct 2023
raitobezarius	I never got this bug and I use quite often the npm-prefetch-deps thingie…	20:55:01
raitobezarius	On a shared machine on top of that where there's like 6TB of nix store…	20:55:12
raitobezarius	(but it's a 1Gbps connection)	20:55:22
Cobalt	In reply to @lily:lily.flowers Could you try the branch linked above too then? Sure, though that it might be delayed until tomorrow.	20:56:39
7 Oct 2023
Marie	I tried it on a nixos vm and as soon as i raised the cpu core count the issue started to appear	12:32:43
Lily Foster	In reply to @marie:marie.cologne I tried it on a nixos vm and as soon as i raised the cpu core count the issue started to appear I'll try to make a branch to confirm whether or not the curl bump is in fact causing this	13:53:53
Cobalt	In reply to @lily:lily.flowers Could you try the branch linked above too then? Unfortunately it threw a `[18] Transferred a partial file` within 10-20 seconds. One time though it got a bit further but stopped with a `[55] Failed sending data to the peer`. Host: NixOS 23.05, on a (congested) 50Mb/s connection, project with a few hundred deps	14:10:43
Cobalt	I haven't tried it with lower cores yet	14:11:11
Cobalt	* I haven't tried it with a lower core count yet	14:11:19
Lily Foster	In reply to @c0ba1t:matrix.org Unfortunately it threw a `[18] Transferred a partial file` within 10-20 seconds. One time though it got a bit further but stopped with a `[55] Failed sending data to the peer`. Host: NixOS 23.05, on a (congested) 50Mb/s connection, project with a few hundred deps Still says "unknown error"?	14:12:13
Lily Foster	In reply to @c0ba1t:matrix.org I haven't tried it with a lower core count yet No need, I'm trying to get failure logs	14:12:35
Cobalt	In reply to @lily:lily.flowers Still says "unknown error"? yep, an excerpt: `[...] node_modules/uri-js Error: unknown error Caused by: [55] Failed sending data to the peer`	14:12:49
Lily Foster	Could someone do it with `RUST_LOG=debug` in the environment too?	14:12:59
Cobalt	In reply to @lily:lily.flowers No need, I'm trying to get failure logs Okay, if you need any logs I would be happy help	14:13:19
Cobalt	Download prefetch-log.txt	14:14:47
Cobalt	That's the output from `RUST_LOG=debug nix run github:lilyinstarlight/nixpkgs/upd/prefetch-npm-deps-deps#prefetch-npm-deps package-lock.json &> prefetch-log.txt`	14:15:32
Lily Foster	I'll check it when I get back to my computer in a bit	14:15:54
Cobalt	Okay, thank you for the quick handling of the issue. Intermittent network stuff is always a tricky	14:16:50
Marie	i have the same openssl broken pipe errors in my log	14:17:53
Lily Foster	I sorta avoided digging in at all for a few weeks, so idk if I'd call that "quick handling" 😅	14:18:00
8 Oct 2023
Lily Foster	In reply to @c0ba1t:matrix.org That's the output from `RUST_LOG=debug nix run github:lilyinstarlight/nixpkgs/upd/prefetch-npm-deps-deps#prefetch-npm-deps package-lock.json &> prefetch-log.txt` Could you try again with `RUST_LOG=debug nix run github:lilyinstarlight/nixpkgs/tmp/fix/prefetch-npm-deps-hell#prefetch-npm-deps package-lock.json &> prefetch-log.txt` for me? I'm testing to see whether or not curl upgrade is the exact cause	22:28:27
Cobalt	Sure,	22:41:21
Cobalt	Download prefetch-log.txt	22:41:22
Cobalt	That's the first run, same failure. I can run it multiple times, if you want more logs.	22:42:06
Cobalt	tl;dr the error wasn't resolved. Here's the tail of the file: [2023-10-08T22:40:40Z DEBUG isahc::handler] h2 [accept-encoding: deflate, gzip, br, zstd] [2023-10-08T22:40:40Z DEBUG isahc::handler] h2 [user-agent: curl/8.2.1 isahc/1.7.2] [2023-10-08T22:40:40Z DEBUG isahc::handler] Using Stream ID: 15 [2023-10-08T22:40:40Z DEBUG isahc::handler] Connection cache is full, closing the oldest one [2023-10-08T22:40:40Z DEBUG isahc::handler] Closing connection [2023-10-08T22:40:40Z DEBUG isahc::handler] Connection #1 to host registry.npmjs.org left intact Error: unknown error Caused by: [55] Failed sending data to the peer	22:44:14
Lily Foster	In reply to @c0ba1t:matrix.org That's the first run, same failure. I can run it multiple times, if you want more logs. Nah, one error is fine, thank you!	22:45:53
Cobalt	Okay, I'll be off for today (it's 1 am in my tz). The error for the above branch is reproducible after every `Connection cache is full, closing the oldest one`. Could there be a race condition between the connection cache being exhausted and accidentally closing an in-use connection?	22:48:58
Cobalt	* Okay, I'll be off for today (it's 1 am in my tz). The error for the above branch is reproducible after every `Connection cache is full, closing the oldest one` message. Could there be a race condition between the connection cache being exhausted and accidentally closing an in-use connection?	22:49:08
Cobalt	Otherwise my first guess would be that the fetcher overallocates ressources. Maybe it tries to allocate all connections and closes a long running, slow connection without checking if it's in use. This wouldn't happen on a fast connection (where a connection is always free) but might be possible with a slow one	22:51:28
Lily Foster	In reply to @c0ba1t:matrix.org Okay, I'll be off for today (it's 1 am in my tz). The error for the above branch is reproducible after every `Connection cache is full, closing the oldest one` message. Could there be a race condition between the connection cache being exhausted and accidentally closing an in-use connection? Well so closing the connection shouldn't even be causing this because it's not doing the retry logic because it doesn't think what is clearly a network error (error code 55) is one and instead treats it as a permanent rather than transient error	22:51:36

Show newer messages

Back to Room ListRoom Version: 6