!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

204 Members
58 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
22 Sep 2023
@mkg20001:mkg20001.iomkg20001there is nodePackages.nodemon, you can install it via nix profile install nixpkgs#nodePackages.nodemon15:22:05
@hexa:lossy.networkhexa
node_modules/rimraf
node_modules/finalhandler/node_modules/ms
node_modules/@histoire/app
Error: unknown error

Caused by:
    [56] Failure when receiving data from the peer
22:41:10
@hexa:lossy.networkhexa😿22:41:13
@hexa:lossy.networkhexatransient22:43:15
@lily:lily.flowersLily FosterIt's supposed to be doing retries :(22:55:31
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
transient
Can you try with RUST_LOG=info in the environment and get it to happen, so I can see if retries are working?
22:56:36
@hexa:lossy.networkhexait worked on my third retry22:57:00
@hexa:lossy.networkhexahence transient 🙂22:57:07
@lily:lily.flowersLily FosterYeah but did you have to rerun the command or no!22:57:28
@lily:lily.flowersLily Foster* Yeah but did you have to rerun the command or no?22:57:34
@lily:lily.flowersLily FosterIt should have some amount of retries built-in22:57:49
@hexa:lossy.networkhexano, it looked like it failed immediately23:01:53
@hexa:lossy.networkhexai reran nix-build23:01:59
@hexa:lossy.networkhexano visible retries23:03:54
@lily:lily.flowersLily FosterWell it propagates the last error if it's retried too many times already, but turning up rust logs would show whether it retried before that23:05:45
@lily:lily.flowersLily FosterHmmm spooky, I'll do some testing later I guess23:06:15
23 Sep 2023
@c0ba1t:matrix.orgCobalt joined the room.18:46:15
24 Sep 2023
@c0ba1t:matrix.orgCobalt
In reply to @hexa:lossy.network
node_modules/rimraf
node_modules/finalhandler/node_modules/ms
node_modules/@histoire/app
Error: unknown error

Caused by:
    [56] Failure when receiving data from the peer

Hey, I had more instances of this and similar dependency fetching errors today. Has anyone figured out (maybe Lily Foster) a workaround?
My first idea was to setup a caching NPM proxy and make the build process temporarily impure.

However this seems to be quite a bit of work and not really treat the root cause (transient fetch error, compared to a working npm install) but only act as a bandaid at best.

18:49:32
@c0ba1t:matrix.orgCobalt* In reply to @hexa:lossy.network node_modules/rimraf node_modules/finalhandler/node_modules/ms node_modules/@histoire/app Error: unknown error Caused by: [56] Failure when receiving data from the peer Hey, I had more instances of this and similar dependency fetching errors today. Has anyone figured out (maybe Lily Foster) a workaround? My first idea was to setup a caching NPM proxy and make the build process temporarily impure. However this seems to be quite a bit of work and not really treat the root cause (transient fetch error, compared to a working npm install) but only act as a bandaid at best. 18:49:45

Show newer messages


Back to Room ListRoom Version: 6