| 26 Nov 2023 |
 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 |
| maralorn | In reply to @sandro:supersandro.de
also you probably don't want to have Werror in nixpkgs That is a very good point. | 18:49:19 |
| Sandro 🐧 | In reply to @sandro:supersandro.de
than I maybe just didn't run into it yet
nix-output-monitor error: DerivationParseError "string"
yet, it is still there
| 22:56:41 |
| Sandro 🐧 | In reply to @maralorn:maralorn.de
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. yeah, sigh. The way to many roots bug is also still there. I just was by accident building things that didn't trigger it. | 22:57:38 |
| maralorn | Sandro 🐧: It should be gone on newest master. | 22:58:29 |
| maralorn | * Sandro 🐧: It should be gone on newest main and in the release. | 22:58:59 |
| Sandro 🐧 | then lets update and see if that is true. Testing qt6 plasma anyway. | 22:59:33 |
 K900 | I haven't hit it since updating, at least | 23:00:05 |
| maralorn | It was important to me to get a working release and stable main branch again. Now I can slowly creep up on the heap of issues that have accumulated over the last year. | 23:01:09 |
| 28 Nov 2023 |
| Sandro 🐧 | 
Download image.png | 08:58:38 |
| Sandro 🐧 | The emoji looks a bit funny but the aligment is correct | 08:58:39 |
| maralorn | Huh, which terminal is that? It's not abiding the spec. | 09:01:35 |
|  @rouven.seifert:matrix.ifsr.de left the room. | 09:13:38 |
| 5 Dec 2023 |
|  @federicodschonborn:matrix.org changed their profile picture. | 00:38:46 |
| 10 Dec 2023 |
|  @mlyx:matrix.org joined the room. | 03:10:36 |
| 11 Dec 2023 |
| @mlyx:matrix.org | Is it possible to detect interactive or not-interactive shell in haskell program? When running in not-interactive shell(github action), it is better to fallback to default nix command output. | 03:26:15 |
| maralorn | If that is possible in any program it should be possible in a Haskell program. | 08:14:58 |
| maralorn | But it's a good idea. | 08:15:46 |
| K900 | @maralorn did you get rid of the eval progress output? | 18:55:03 |
| maralorn | K900 ⚡️: Kinda. I never released it and it was sadly very tangled with another change which really anoyed people. | 21:31:14 |
| maralorn | So before doing the next release I reverted that again. | 21:31:43 |
| maralorn | But that code is still around and I really want to reintroduce it. | 21:32:00 |
