Nix NodeJS | 209 Members | |
| 59 Servers |
| Sender | Message | Time |
|---|---|---|
| 22 Sep 2023 | ||
| 11:21:29 | ||
| 11:23:14 | ||
| there is nodePackages.nodemon, you can install it via nix profile install nixpkgs#nodePackages.nodemon | 15:22:05 | |
| 22:41:10 | |
| 😿 | 22:41:13 | |
| transient | 22:43:15 | |
| It's supposed to be doing retries :( | 22:55:31 | |
In reply to @hexa:lossy.networkCan 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 | |
| it worked on my third retry | 22:57:00 | |
| hence transient 🙂 | 22:57:07 | |
| Yeah but did you have to rerun the command or no! | 22:57:28 | |
| * Yeah but did you have to rerun the command or no? | 22:57:34 | |
| It should have some amount of retries built-in | 22:57:49 | |
| no, it looked like it failed immediately | 23:01:53 | |
| i reran nix-build | 23:01:59 | |
| no visible retries | 23:03:54 | |
| 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 | |
| Hmmm spooky, I'll do some testing later I guess | 23:06:15 | |
| 23 Sep 2023 | ||
| 18:46:15 | ||
| 24 Sep 2023 | ||
In reply to @hexa:lossy.network Hey, I had more instances of this and similar dependency fetching errors today. Has anyone figured out (maybe Lily Foster) a workaround? However this seems to be quite a bit of work and not really treat the root cause (transient fetch error, compared to a working | 18:49:32 | |
| * 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 | |
| * 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 | |
In reply to @lily:lily.flowerscan you still reproduce this? if so please rerun with this env var | 18:50:14 | |
| * 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 | |
| 26 Sep 2023 | ||
| how would one go about adding a package to a package.json at build time? | 00:22:57 | |
In reply to @emma:rory.gayDepends, why is it needed? | 10:11:59 | |
i want to add the pg library specifically in nix | 10:12:45 | |
| youre "supposed to install it yourself if you want postgres" | 10:13:04 | |
| Like the C library or some npm package? | 10:14:20 | |
| the npm package | 10:14:31 | |