| 12 Sep 2023 |
 @vid:matrix.org | * oic, also "not the nixos way" | 14:33:14 |
| 13 Sep 2023 |
|  mkg20001 joined the room. | 09:18:14 |
| 15 Sep 2023 |
| @vid:matrix.org | I think I found a good solution, distrobox. I used the unstable channel, separate home directory, hard coded my PATH (even though latest distrobox is not supposed to include host binaries). don't want to push my luck so knock wood, but I've been able to use it like a distinct environment, including x11 forwarding to the host, which is the dream | 12:51:07 |
| @vid:matrix.org | iow I'm living the dream | 12:51:27 |
| @vid:matrix.org | could have just used containers on their own but this takes away a lot of the wtf | 12:52:20 |
| 21 Sep 2023 |
|  dedmunwalk joined the room. | 23:09:32 |
| 22 Sep 2023 |
|  bl1nk changed their profile picture. | 11:21:29 |
| bl1nk changed their profile picture. | 11:23:14 |
| mkg20001 | there is nodePackages.nodemon, you can install it via nix profile install nixpkgs#nodePackages.nodemon | 15:22:05 |
 hexa | 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 | 😿 | 22:41:13 |
| hexa | transient | 22:43:15 |
 Lily Foster | It's supposed to be doing retries :( | 22:55:31 |
| Lily 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 | it worked on my third retry | 22:57:00 |
| hexa | hence transient 🙂 | 22:57:07 |
| Lily Foster | Yeah but did you have to rerun the command or no! | 22:57:28 |
| Lily Foster | * Yeah but did you have to rerun the command or no? | 22:57:34 |
| Lily Foster | It should have some amount of retries built-in | 22:57:49 |
| hexa | no, it looked like it failed immediately | 23:01:53 |
| hexa | i reran nix-build | 23:01:59 |
| hexa | no visible retries | 23:03:54 |
| Lily Foster | Well it propagates the last error if it's retried too many times already, but turning up rust logs would show whether it retried before that | 23:05:45 |
| Lily Foster | Hmmm spooky, I'll do some testing later I guess | 23:06:15 |
| 23 Sep 2023 |
|  Cobalt joined the room. | 18:46:15 |
| 24 Sep 2023 |
| Cobalt | 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 |
| Cobalt | * 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 |
| Cobalt | *
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:50:14 |
| hexa | In reply to @lily:lily.flowers
Can you try with RUST_LOG=info in the environment and get it to happen, so I can see if retries are working? can you still reproduce this? if so please rerun with this env var | 18:50:14 |
| Cobalt | * In reply to hexa
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 instead only act as a bandaid. | 18:51:22 |
