| 23 Nov 2023 |
 maralorn | * If anyone wants to try current nom main branch out, that'd be great. There are some subtle changes there and I want to do a release soon. | 00:23:00 |
|  @rouven:rfive.de joined the room. | 10:32:24 |
| 25 Nov 2023 |
|  @10leej:matrix.org joined the room. | 15:56:49 |
| 26 Nov 2023 |
 Sandro 🐧 | Did you fix that nom thinks there are way more roots than there actually are? aka https://github.com/maralorn/nix-output-monitor/commit/90fd896e82ce8fe1faa439d3024e950ae488da54 | 03:17:55 |
| Sandro 🐧 | seems to be a lot more stable and predictable. Also the ca errors seem to be gone for the moment but maybe things that use ca are currently cached for me. | 03:20:17 |
| maralorn | In reply to @sandro:supersandro.de
Did you fix that nom thinks there are way more roots than there actually are? aka https://github.com/maralorn/nix-output-monitor/commit/90fd896e82ce8fe1faa439d3024e950ae488da54 I tried to. The other day I saw a screenshot by hexa which made me believe I failed. | 08:42:01 |
| maralorn | I am relatively certain, that I didn't fix the CA error. | 08:43:03 |
| maralorn | Although actually the might also be a problem with how nixpkgs review works now that I think about it. | 08:49:56 |
| maralorn | Ah, no. I think I know the issue now. | 08:51:36 |
| maralorn | So: That change introduces the bug because it makes sure all builds and downloads get displayed. Even those which cannot be displayed in the tree. Previously those were simply hidden. | 08:53:29 |
| maralorn | No, that also doesn't make sense. | 08:54:04 |
| maralorn | Oh, man I am grasping. It's too long ago I wrote that code. | 08:54:32 |
| maralorn | Maybe that bug can also only occur when remote building? | 08:59:20 |
| maralorn | New release of nix-output-monitor: https://github.com/NixOS/nixpkgs/pull/270161 | 15:33:15 |
| maralorn | Sadly I had to roll back a few recent improvements because I had only the choice between behaviour regressions or performance regressions. I think I know how to fix that, but I didn’t want to delay the release anymore. | 15:35:11 |
| maralorn | * Sadly I had to roll back a few recent unreleased improvements because I had only the choice between behaviour regressions or performance regressions. I think I know how to fix that, but I didn’t want to delay the release anymore. | 15:35:21 |
| maralorn | * Sadly I had to roll back a few recent unreleased improvements because I had only the choice between behaviour regressions or performance regressions. I think I know how to fix that, but that is more engineering work I didn’t want to delay the release anymore. | 15:35:39 |
| maralorn | * Sadly I had to roll back a few recent unreleased improvements because I had only the choice between behaviour regressions or performance regressions. I think I know how to fix that, but that is more engineering work and I didn’t want to delay the release anymore. | 15:35:46 |
| Sandro 🐧 | In reply to @maralorn:maralorn.de
I am relatively certain, that I didn't fix the CA error. than I maybe just didn't run into it yet | 17:36:28 |
| Sandro 🐧 | is that new, that those internal things are displayed?
➜ nix build .#openjpeg.dev
⏱ 3s evaluating, 1 files so far, last one was '/derivation-internal.nix | 17:36:40 |
| Sandro 🐧 | In reply to @maralorn:maralorn.de
Maybe that bug can also only occur when remote building? I am usually remote building a lot | 17:37:12 |
| Sandro 🐧 | I am still on the commit from yesterday | 17:39:09 |
| Sandro 🐧 | also you probably don't want to have Werror in nixpkgs | 17:39:46 |
| maralorn | In reply to @sandro:supersandro.de
is that new, that those internal things are displayed?
➜ nix build .#openjpeg.dev
⏱ 3s evaluating, 1 files so far, last one was '/derivation-internal.nix Yes, that has not reached any release and I have actually reverted it because it correlates with some troubale. | 18:44:21 |
| maralorn | In reply to @sandro:supersandro.de
I am usually remote building a lot I understand. But ssh-ng was never properly supported by nom in a way, that when remote building a lot of the internal state of nom is fucked. This means that display will be wrong and confusing in a lot of ways. | 18:46:22 |
| maralorn | In reply to @sandro:supersandro.de
I am usually remote building a lot * I understand. But ssh-ng was never properly supported by nom in a way, that when remote building a lot of the internal state of nom is fucked. This means that display will be wrong and confusing in a lot of ways. | 18:47:07 |
