| 6 May 2023 |
hexa | so we mostly decided to drop things ahead of the release | 13:48:59 |
Lily Foster | Looks like they has RSS for their announcements. I'll add it to my rss2email config I guess | 13:49:28 |
Lily Foster | * Looks like they have RSS for their announcements. I'll add it to my rss2email config I guess | 13:49:39 |
hexa | bitwarden fails to build with nodejs 18 😄 | 13:50:03 |
hexa | bitwarden> /nix/store/pgf87rgkzdbqhhsddpligy8xiwar63w8-stdenv-linux/setup: line 122: Unknown command: "bin"
| 13:50:14 |
hexa | *
bitwarden> /nix/store/pgf87rgkzdbqhhsddpligy8xiwar63w8-stdenv-linux/setup: line 122: Unknown command: "bin"
| 13:50:17 |
Lily Foster | In reply to @hexa:lossy.network bitwarden fails to build with nodejs 18 😄 Oh, I know. I know a few things that will | 13:50:26 |
Lily Foster | Especially C/++ modules | 13:50:40 |
Lily Foster | In reply to @hexa:lossy.network
bitwarden> /nix/store/pgf87rgkzdbqhhsddpligy8xiwar63w8-stdenv-linux/setup: line 122: Unknown command: "bin"
Okay that's... a weird error... | 13:50:59 |
hexa |
To see a list of supported npm commands, run: npm help/electron-builder: No such file or directory
| 13:51:29 |
hexa | continues like that | 13:51:31 |
Lily Foster | I guess I'll actually get out my laptop | 13:52:09 |
@ambroisie:belanyi.fr | I saw tandoor-recipes in your list, just updated my version bump PR to use nodejs 😉 | 16:56:22 |
| 8 May 2023 |
| aktaboot joined the room. | 20:44:24 |
aktaboot | In reply to @lily:lily.flowers We, uh, should probably make tooling to handle those soon can I open an issue about this ? 👀 | 20:53:07 |
Lily Foster | In reply to @aktaboot:tchncs.de can I open an issue about this ? 👀 Yeah, I can do that in a bit | 21:01:51 |
| 9 May 2023 |
| denbrahe joined the room. | 10:30:01 |
denbrahe | Hi, I'm trying to create a derivation for a React package using buildNpmPackage. However, both buildNpmPackage and prefetch-npm-deps always fail with Error: https://registry.npmjs.org/@babel/eslint-parser/-/eslint-parser-7.19.1.tgz: Connection Failed: tls connection init failed: Connection reset by peer (os error 104). Which package failed varies between retries. What could cause that? | 10:34:20 |
Lily Foster | In reply to @denbrahe:matrix.org Hi, I'm trying to create a derivation for a React package using buildNpmPackage. However, both buildNpmPackage and prefetch-npm-deps always fail with Error: https://registry.npmjs.org/@babel/eslint-parser/-/eslint-parser-7.19.1.tgz: Connection Failed: tls connection init failed: Connection reset by peer (os error 104). Which package failed varies between retries. What could cause that? Sometimes the registry connection fails or gets dropped on wifi for me. Retry until it works I guess. I plan to add retry logic to the fetcher so those transient error don't cause the entire fetch to fail | 10:46:39 |
Lily Foster | It fetches in parallel, so you might be able to set --cores 1 on the nix build command to disable that (I forget if it respects that or not) | 10:47:14 |
denbrahe | Ok, thank you! If I understand correctly, prefetch-npm-deps adds the cache to the Nix store, so if I get prefetch-npm-deps to work buildNpmPackage should also work? | 10:52:13 |
Lily Foster | It does not add it to the store by default | 10:56:12 |
Lily Foster | You'd have to actually use nix build for it to go to the store | 10:56:32 |
denbrahe | Okay, I'll just loop nix-build then. Thanks! | 10:57:49 |
Lily Foster | Try --cores 1 on your nix-build command if you haven't already, since that might help | 10:58:45 |
Lily Foster | (Or maybe it's only --option cores 1 for the old cli... i forget) | 10:59:11 |
denbrahe | I'll try both 😛 | 11:03:40 |
denbrahe | 100 retries, got nothing. Is this normal? It's a small project, only notable deps are react and typescript | 11:32:01 |
Lily Foster | Nope that's not normal. I'll see if I can get retry logic working today and will let you try it, if you can't get a successful build before then | 11:42:27 |
Lily Foster | Also if it's ignoring nix's NUM_JOBS setting then I'll fix that too | 11:42:42 |