| 31 Oct 2023 |
 Wanja Hentze | yes it does fetch in parallel, that is part of the problem | 19:52:55 |
 Lily Foster | What nixpkgs branch are you working off of? | 19:53:08 |
| Wanja Hentze | uhh unstable but this was a couple weeks ago | 19:53:29 |
| Wanja Hentze | I could try again | 19:53:36 |
| Lily Foster | rev? | 19:53:58 |
| Wanja Hentze | dunno, I'm on the phone | 19:54:07 |
| Lily Foster | these fixes were all merged more than a few weeks ago i thought | 19:54:08 |
| Wanja Hentze | sry | 19:54:13 |
| Lily Foster | no it's okay! | 19:54:16 |
| Lily Foster | i'm just confused 😅 | 19:54:20 |
| Wanja Hentze | very possible that they have | 19:54:25 |
| Lily Foster | Well I think the retries failing for response bodies issue was more recent | 19:54:46 |
| Wanja Hentze | another weird failure mode we saw: the fetcher seemed to ignore HTTP 4XX from the remote and would just try to decode the body (which was text/html saying "permission denied" or sth) as a tarball | 19:55:22 |
| Wanja Hentze | maybe that's fixed too | 19:55:36 |
| Lily Foster | quite possibly? i do appreciate you bringing these issues up though | 19:55:50 |
| Lily Foster | do you think when you run into them you could open nixpkgs issues and ping me and/or the node team on thme? | 19:56:01 |
| Lily Foster | * do you think when you run into them you could open nixpkgs issues and ping me and/or the node team on them? | 19:56:02 |
| Lily Foster | we are very interesting in fixing stuff like that | 19:56:09 |
| Lily Foster | * we are very interested in fixing stuff like that | 19:56:13 |
| Wanja Hentze | In reply to @lily:lily.flowers
do you think when you run into them you could open nixpkgs issues and ping me and/or the node team on them? yes | 19:56:24 |
| Wanja Hentze | for now I'm still trying to make dream2nix work though | 19:56:43 |
| Wanja Hentze | because I really really want to not prefetch | 19:56:51 |
| Lily Foster | Would you be interested in testing importNpmLock functionality when we have that ready? It'll function similarly to the importCargoLock tooling from rust and won't require prefetched FODs | 19:57:37 |
| Wanja Hentze | oh nice | 20:12:10 |
| Wanja Hentze | yes for sure! | 20:12:13 |
 daniel | In reply to @emma:conduit.rory.gay
hint: i had to write my own derivation to get it to work Off topic but is this really true? I mean, there is this: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/dotnet.section.md#using-many-sdks-in-a-workflow-using-many-sdks-in-a-workflow | 20:17:17 |
| Wanja Hentze | In reply to @lily:lily.flowers
(tbh the nixpkgs one would be a lot better if i either had time or someone else to collaborate on it with too...) we can also collaborate when I have time again. I don't know too much npm stuff but am decent at nix and rust | 20:17:41 |
 @joepie91:pixie.town | In reply to @whentze:matrix.org
joepie91 🏳️🌈: so which of the ~dozen or so npm/nix things should I use well that I can't exhaustively answer :p I've been using yarn2nix and that has worked Well Enough so far (I use yarn v1 due to some functionality in npm being broken since forever) | 20:26:18 |
| Wanja Hentze | oh true that exists too | 20:27:32 |
| @joepie91:pixie.town | (also, an issue I've had with some npm/nix tooling in the past was that it went off package.json, and expected you to pre-generate a nix expression in the project's repository. which is not helpful when it's not your project... yarn2nix seems to have no trouble dealing with third-party lockfiles at evaluation time) | 20:29:45 |
