Nix NodeJS | 206 Members | |
| 59 Servers |
| Sender | Message | Time |
|---|---|---|
| 24 Jul 2023 | ||
*
| 08:45:42 | |
| I can take a look later at this, maybe you can already create a PR. Thanks for digging into this | 09:56:34 | |
| 25 Jul 2023 | ||
| 01:56:41 | ||
| Uh, have we found a solution out of the missing integrity debacle? | 17:23:57 | |
| upstream issues seems to be going nowhere | 17:27:27 | |
something like cargoLock.outputHashes would be great | 17:28:55 | |
| I can create an issue, if we want to track this better than me rambling in this room | 17:29:26 | |
In reply to @hexa:lossy.networkYeah, feel free to make an issue and add it to our To-Do project board and ping me. I have a rough plan that I can outline in the issue, but I just need to sit down and finish refactoring prefetch-npm-deps enough to implement it (so having an issue to track is probably a good idea) | 20:20:55 | |
| threading time, it seems build is failing on hydra again? | 22:51:47 | |
| but it just built fine on my system | 22:51:56 | |
| 27 Jul 2023 | ||
| 03:04:29 | ||
| 28 Jul 2023 | ||
| gdamjan: incoming security issues for several appservices | 14:22:23 | |
Download image.png | 14:22:24 | |
| wondering if you can expedite your efforts 😕 | 14:22:36 | |
| :/ | 14:22:43 | |
| did go too far | 14:22:47 | |
| * didn't go too far | 14:22:53 | |
| whatever happened with that yarn2nix issue? | 15:11:16 | |
In reply to @gdamjan:spodeli.orgWhich one? | 15:22:56 | |
| For v2 lockfiles? | 15:23:01 | |
no, it was about installing only the older version of a dependency when there were two versions of ajv in yarn.lock (one is direct dependency, the other is a deep dependency) | 15:25:23 | |
Oh, is it a yarn2nix problem or fetchYarnDeps problem? (If there is an open nixpkgs issue can you link it so I can add it to our project board too?) | 15:26:25 | |
| there probably isn't. not by me anyway | 15:27:00 | |
In reply to @gdamjan:spodeli.orgIf you have the relevant info, would you mind opening one so I can add it then? Thank you! ❤️ | 15:27:50 | |
| yeah sure. can you send me a similar bug report so I know not to miss anything? | 15:28:32 | |
it's a yarn2nix issue (it's what mkYarnPackage is using right) | 15:29:56 | |
In reply to @gdamjan:spodeli.orgYou can use fetchYarnDeps with mkYarnPackage (in fact I'm pretty sure it was added originally for that reason, to avoid needing to vendor yarn.lock/yarn.nix when using mkYarnPackage). But if you aren't using fetchYarnDeps anywhere then yeah it's strictly a yarn2nix problem | 15:32:12 | |
In reply to @gdamjan:spodeli.org I mean here was a recent nodejs-related issue, if that's what you're asking for: https://github.com/NixOS/nixpkgs/issues/244285 I mostly just want a derivation to reproduce | 15:36:06 | |
| damn, I've deleted my failed try when I was trying other approaches | 15:36:32 | |
| I'll re-create it later | 16:00:34 | |