| 30 Jun 2024 |
|  @pkolloch:matrix.org left the room. | 09:02:47 |
| 1 Jul 2024 |
 hexa | django-hijack> Installing dependencies
django-hijack> npm WARN deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
django-hijack> npm WARN deprecated domexception@4.0.0: Use your platform's native DOMException instead
django-hijack> npm ERR! code ENOTCACHED
django-hijack> npm ERR! request to https://registry.npmjs.org/yocto-queue failed: cache mode is 'only-if-cached' but no cached response is available.
django-hijack>
django-hijack> npm ERR! A complete log of this run can be found in: /build/cache/_logs/2024-07-01T00_08_16_686Z-debug-0.log
| 00:10:43 |
| hexa | https://github.com/django-hijack/django-hijack/blob/3.5.4/package-lock.json#L8899 | 00:11:13 |
| hexa | why doesn't it fetch yocto-queue? 🤔 | 00:11:28 |
| hexa | not resolved, no integrity hash | 00:15:07 |
| 2 Jul 2024 |
|  Aldwin joined the room. | 15:34:02 |
| Aldwin | Hi all. A quick question: When I spawn a devShell with pkgs.nodePackages.yarn.override { nodejs = pkgs.nodejs-18_x; } as one of the packages, and run yarn exec -- node --version, the installed node version is 20.12.2. I expect to get 18.x there. What am I doing wrong? | 15:34:58 |
 Lily Foster | you probably want pkgs.yarn. i didn't even know we still had a nodePackages.yarn and we really shouldn't | 15:37:02 |
| Aldwin | oh! o.o haha thanks! | 15:37:43 |
| Aldwin | That does the trick. I remember not finding pkgs.yarn though, like, I think I fell back on nodePackages.yarn if I remember rightly. Oh well. 🤷 | 15:39:02 |
| 3 Jul 2024 |
|  @maertens:matrix.org joined the room. | 19:00:16 |
| 4 Jul 2024 |
|  Jack joined the room. | 07:05:04 |
|  junglerobba joined the room. | 09:40:10 |
| 8 Jul 2024 |
|  Nick Kadutskyi joined the room. | 19:30:13 |
| 9 Jul 2024 |
|  emily joined the room. | 12:16:54 |
| emily | not sure if there's anyone familiar with the Node tests, but I'm trying to diagnose the failures of nodejs_{18,20} on x86_64-darwin (https://hydra.nixos.org/build/265094929/nixlog/3, https://hydra.nixos.org/build/264956149/nixlog/3) and I'm stumped. it seems to be some weird nondeterministic flakiness; the test suite runs for ages and then suddenly stops being able to find out/Release/node, which definitely exists before the tests start running | 12:19:33 |
| emily | locally I get through many more tests, but still eventually have some fail because of that. I also get some strange readv test failures (AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal: 54 !== 109) | 12:20:42 |
| emily | what confuses me is that it seems to have been working fine before this, so presumably something about the recent staging merge made things a lot more unreliable, but I don't really have any clue what it could be | 12:21:04 |
| emily | (and it's fine on aarch64-darwin too) | 12:21:50 |
| emily | oh, apparently most of these tests only started running recently: https://github.com/NixOS/nixpkgs/pull/313982 | 12:23:19 |
| emily | I might just switch them off on Darwin for now then :( | 12:24:52 |
| 10 Jul 2024 |
|  atagen joined the room. | 04:54:29 |
