| 10 Aug 2023 |
 countoren | o that make sense | 01:12:04 |
 Lily Foster | You should see a bunch of isahc:debug log statements | 01:12:06 |
| Lily Foster | If that's not enough I might ask for a RUSTLOG=trace too | 01:12:26 |
| Lily Foster | (It's also 21:12 here so I'm going to sleep in a few, but I'll be able to respond more in the morning) | 01:13:14 |
| Lily Foster | (I'm assuming something's wonky with the http header or maybe I typo'd it) | 01:13:36 |
| countoren | no isahc:debug | 01:14:56 |
| Lily Foster | Hmmm 🤔, I'll do some of my own testing tomorrow and get some logs | 01:15:33 |
| countoren | npm WARN tar TAR_BAD_ARCHIVE: Unrecognized archive format
npm WARN tarball cached data for @fortawesome/fontawesome-svg-core@https://npm.fontawesome.com/@fortawesome/fontawesome-svg-core/-/1.2.30/fontawesome-svg-c>
npm WARN tar TAR_BAD_ARCHIVE: Unrecognized archive format
npm WARN tarball cached data for @fortawesome/angular-fontawesome@https://npm.fontawesome.com/@fortawesome/angular-fontawesome/-/angular-fontawesome-0.5.0.>
npm verb stack Error: EACCES: permission denied, unlink '/nix/store/zs3dw8r0b79235mnhy55bc3am67li6yr-client-0.0.0-npm-deps/_cacache/content-v2/sha512/fb/1b>
npm verb cwd /build/server
npm verb Linux 5.15.103
npm verb node v18.16.1
npm verb npm v9.5.1
npm ERR! code EACCES
npm ERR! syscall unlink
npm ERR! path /nix/store/zs3dw8r0b79235mnhy55bc3am67li6yr-client-0.0.0-npm-deps/_cacache/content-v2/sha512/fb/1b/636c8cbf6e3cece11bffdb6eee3c943e6f818d76b5>
npm ERR! errno -13
npm verb Error: EACCES: permission denied, unlink '/nix/store/zs3dw8r0b79235mnhy55bc3am67li6yr-client-0.0.0-npm-deps/_cacache/content-v2/sha512/fb/1b/636c8>
npm ERR!
npm ERR! Your cache folder contains root-owned files, due to a bug in
npm ERR! previous versions of npm which has since been addressed.
npm ERR!
npm ERR! To permanently fix this problem, please run:
npm ERR! sudo chown -R 1000:100 "/nix/store/zs3dw8r0b79235mnhy55bc3am67li6yr-client-0.0.0-npm-deps"
npm verb exit -13
npm verb unfinished npm timer reify 1691629999709
npm verb unfinished npm timer reify:unpack 1691630000039
npm verb unfinished npm timer reifyNode:node_modules/@fortawesome/pro-solid-svg-icons 1691630000170
npm verb unfinished npm timer reifyNode:node_modules/@fortawesome/pro-light-svg-icons 1691630000170
npm verb unfinished npm timer reifyNode:node_modules/@fortawesome/fontawesome-svg-core 1691630000170
npm verb unfinished npm timer reifyNode:node_modules/@fortawesome/fontawesome-common-types 1691630000170
npm verb unfinished npm timer reifyNode:node_modules/@fortawesome/angular-fontawesome 1691630000170
npm verb code -13
npm ERR! Log files were not written due to an error writing to the directory: /nix/store/zs3dw8r0b79235mnhy55bc3am67li6yr-client-0.0.0-npm-deps/_logs
npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
ERROR: npm failed to install dependencies
Here are a few things you can try, depending on the error:
1. Set `makeCacheWritable = true`
Note that this won't help if npm is complaining about not being able to write to the logs directory -- look above that for the actual error.
2. Set `npmFlags = [ "--legacy-peer-deps" ]`
lines 32-70/71 100%
| 01:15:50 |
| countoren | from nix log | 01:15:55 |
| countoren | i can show the first 32 lines too if you need | 01:16:33 |
| countoren | np | 01:16:47 |
| countoren | Lily Foster: Thank you for your help | 01:21:35 |
 @gdesforges:matrix.org | Lily Foster: I've tested manually marp-cli from your Nix code and it works well 🎉 I've pushed a PR. Are you the one who can approve? https://github.com/NixOS/nixpkgs/pull/248107 | 10:14:12 |
| @gdesforges:matrix.org | * Lily Foster: I've tested manually marp-cli from your Nix code and it works well 🎉 I've pushed a PR. Are you the one who can approve and merge? https://github.com/NixOS/nixpkgs/pull/248107 | 10:14:25 |
| Lily Foster | In reply to @gdesforges:matrix.org
Lily Foster: I've tested manually marp-cli from your Nix code and it works well 🎉 I've pushed a PR. Are you the one who can approve and merge? https://github.com/NixOS/nixpkgs/pull/248107 Yep, I can. Request my review and I'll try to get to it today | 10:15:11 |
 dotlambda | Ambroisie: Does pnpm-lock-export need internet access and does it have a reproducible output? | 16:41:27 |
 @ambroisie:belanyi.fr | In reply to @robert:funklause.de
Ambroisie: Does pnpm-lock-export need internet access and does it have a reproducible output?
- I don't think so
- I think so
But I haven't checked either
| 16:51:33 |
| @ambroisie:belanyi.fr | * In reply to @robert:funklause.de
Ambroisie: Does pnpm-lock-export need internet access and does it have a reproducible output?
I don't think so
I think so
But I haven't checked either
| 16:51:50 |
| @ambroisie:belanyi.fr | Urgh, the formatting is absolutely screwed up | 16:52:06 |
| dotlambda | So why use it in the update script rather than postPatch? | 16:59:12 |
| @ambroisie:belanyi.fr | Because I don't want to find out that either point is wrong :') | 17:01:15 |
| dotlambda | Haha | 17:01:41 |
| Lily Foster | It does lockfile v1 output so npm can still get spooked. It should be deterministic but may not be reproducible across versions so doing it in updateScript is probably a better idea | 17:05:24 |
| dotlambda | What does "reproducible across versions" mean? | 17:13:35 |
| dotlambda | Using it in an updateScript has the big disadvantage of having to commit thousands of lines of code to nixpkgs. | 17:13:35 |
| dotlambda | In reply to @robert:funklause.de
What does "reproducible across versions" mean? Oh, across versions of pnpm-lock-export | 17:16:33 |
| Lily Foster | In reply to @robert:funklause.de
What does "reproducible across versions" mean? Like if the output is one way in version 1.0 but then later if the package is updated to 2.0, the output could be subtly different (ask me how I've become paranoid about this 🙃) | 17:16:53 |
| Lily Foster | In reply to @robert:funklause.de
Oh, across versions of pnpm-lock-export Yeah | 17:16:56 |
| Lily Foster | * In reply to @robert:funklause.de
What does "reproducible across versions" mean?
Like if the pnpm-lock-export output is one way in version 1.0 but then later if the package is updated to 2.0, the output could be subtly different (ask me how I've become paranoid about this 🙃) | 17:17:08 |
| dotlambda | That could be remediated by using different attributes in all-packages.nix for different versions | 17:18:23 |
