| 4 May 2023 |
 Lily Foster | Derivation? | 23:54:21 |
 hexa | well, before it failed while fetching | 23:54:50 |
| hexa | so maybe this is due to the package itself | 23:54:58 |
| Lily Foster | (I tested these PRs way too much for this ðŸ˜) | 23:55:01 |
| hexa | https://github.com/NixOS/nixpkgs/pull/229953 | 23:55:01 |
| Lily Foster | In reply to @hexa:lossy.network
well, before it failed while fetching Was it a timeout? We need to put shorter timeout and retry logic into the fetcher because I've found at least one package often gets lost when it tries to parallel grab everything | 23:55:38 |
| hexa | see the PR description | 23:55:50 |
| hexa |
navidrome-ui> npm ERR! request to https://registry.npmjs.org/color-name/-/color-name-1.1.3.tgz failed: cache mode is 'only-if-cached' but no cached response is available.
| 23:56:11 |
| hexa | basically this | 23:56:13 |
| Lily Foster | Oh that's during dep build, not during fetching. And yeah that is what the just-merged PR should fix | 23:56:33 |
| hexa | it did. | 23:56:52 |
| hexa | have been waiting for this change since the end of january 😄 | 23:57:03 |
| hexa | okay, nvm | 23:57:12 |
| hexa | deleted my postInstall thing and tada.wav | 23:57:24 |
| hexa | so let me retry with overwriting the complete installPhase | 23:58:06 |
| Lily Foster | I just checked the package-lock.json and no git deps so you shouldn't need https://github.com/NixOS/nixpkgs/pull/206477 at least. I plan to get that one in too in the next week. I pushed what is hopefully the final diff a bit ago, but I need to do testing to make sure it is actually working as intended | 23:58:53 |
| 5 May 2023 |
| hexa | I also had one that had a git dependency | 00:06:53 |
| hexa | but it is so long ago, I don't even remember which one it was | 00:07:02 |
| hexa | navidrome ui looks good. | 00:07:28 |
| Lily Foster | In reply to @hexa:lossy.network
but it is so long ago, I don't even remember which one it was Hopefully those will work okay enough soon.... Npm just keeps finding new and surprising ways to make those utterly busted though | 00:08:41 |
| hexa | thanks for working on these issues nevertheless | 00:09:03 |
| Lily Foster | (after 206477 and some code to deal with npm workspaces, I will consider npm stuff "reasonably usable" -- right now it's pretty hit-or-miss though and obviously we would still have yarn, pnpm, etc to deal with once npm is fine) | 00:10:16 |
| Lily Foster | * (after #206477 and some code to deal with npm workspaces, I will consider npm stuff "reasonably usable" -- right now it's pretty hit-or-miss though and obviously we would still have yarn, pnpm, etc to deal with once npm is fine) | 00:10:21 |
| hexa | indeed, looking forward to yarn, to build home-assistants ui from source | 00:10:41 |
| hexa | and then we can hopefully tackle most of nodePackages | 00:10:55 |
| hexa | ideally we would just mark all of nodePackages broken at some point | 00:11:14 |
| Lily Foster | Yeah, I have two open fixes to the fetchYarnDeps fetcher and then we can make those work with buildYarnPackage and then no more yarn2nix-moretea or whatever it's called now | 00:11:26 |
| hexa | yeah, I've used yarn2nix-moretea and the defaults are borderline IFD | 00:11:55 |
| hexa | * yeah, I've used yarn2nix-moretea and its defaults are borderline IFD | 00:13:12 |
| Lily Foster | In reply to @hexa:lossy.network
navidrome ui looks good. When/how did you get that npmDepsHash? I'm getting a different one locally | 00:16:13 |
