| 17 Nov 2025 |
 maralorn | Huh, that would be easier, true. | 21:59:07 |
| 18 Nov 2025 |
 hexa | there are builds that log a percentage progress | 00:48:59 |
| hexa | e.g. cmake builds go [ 23%] foobar [100%] every few lines | 00:49:24 |
| hexa | * e.g. cmake builds go [ 23%] foobar [100%] foobar every few lines | 00:49:31 |
| hexa | that would be a worthwhile thing to display, I think | 00:49:44 |
| hexa | or bazel | 00:49:51 |
| hexa | which logs [67/2202] (done/total) | 00:50:53 |
| hexa | although total can grow | 00:50:59 |
| hexa | both of these are logged at the start of a line | 00:51:10 |
| hexa | so maybe just add build progress when you can derive it from the log | 00:51:35 |
| hexa | and if you know phases you can even show build and test progress | 00:51:57 |
| hexa | * and if you know phases you could even show build and test progress | 00:52:01 |
| hexa | requests> ........................................................................ [ 28%]
requests> ........................................................................ [ 56%]
requests> ..................................................sssssssssss.....s..... [ 84%]
| 00:52:30 |
| hexa | for pytest | 00:52:33 |
| hexa | this could compensate for fast scrolling logs 🙂 | 00:52:59 |
 vivekanandan_ks | U mean the overall progress in percentage instead of just numbers?
I mean like below for downloads, builds, overall progress?
downloads [50/100] 50%
Or u mean for individual package builds?🤔
| 06:08:32 |
| maralorn | I am quite open for implementing custom parsers for popular build tools. | 08:43:07 |
| maralorn | I mean I guess cabal is enough, right? | 09:01:53 |
| maralorn | Hostnames have been ambiguated. | 18:39:12 |
| maralorn | The algorithm is terrible. | 18:39:29 |
| maralorn | But I couldn’t find an elegant solution. | 18:39:58 |
 Emma [it/its] | (\w\d?)(..)* | 20:29:39 |
| Emma [it/its] | * (\w\d?)\(\..)* | 20:29:43 |
| Emma [it/its] | wait, that wouldnt work, but my point was selecting first char for each domain part and maybe including a number if one exists in the first part | 20:30:32 |
| Emma [it/its] | or maybe just always include the full first part? (ie. mouse2.build.nixos.org -> mouse2.b.n.o) | 20:32:28 |
| hexa | I think a stable length helps with layouting | 21:05:14 |
| hexa | and the hostname (the first part of the fqdn) can be up to 65 chars long | 21:05:36 |
| maralorn | Let me rephrase. I think actually the specification I chose is fine. Sadly implementing the specification felt relatively pedestrian and is at least quadratic in the number of hostnames. | 21:16:45 |
| maralorn | Anyway, let me know what you think. | 21:17:08 |
|  dave :3 joined the room. | 22:59:04 |
