| 5 Mar 2025 |
 Picnoir | * (smooth, almost not super pushy :P) | 13:53:39 |
 maralorn | Yeah, we have multiple things on the list which could approve on that. | 15:14:45 |
| maralorn | I feel really bad that I didn’t get to that review, yet. At the time I just didn’t have the time and I keep pushing it off because it feels kinda like a big change and I don’t wanna get it wrong … | 15:16:40 |
| Picnoir | In reply to @maralorn:maralorn.de
I feel really bad that I didn’t get to that review, yet. At the time I just didn’t have the time and I keep pushing it off because it feels kinda like a big change and I don’t wanna get it wrong … Don’t, this is volonteer work, you don’t owe a review. | 15:25:06 |
| Picnoir | I can use my fork in the meantime :) | 15:25:30 |
| 7 Mar 2025 |
 hexa | 
Download image.png | 08:53:39 |
| hexa | collection of traces, warnings, error is such a great feature | 08:53:47 |
| hexa | thanks! | 08:53:58 |
| maralorn | hexa: I am on current main where the "fix" is included and I have the feeling my file is stale again. | 12:37:16 |
| maralorn | On the plus side: I have not the only one line situation but the file is not being touched at all situation. | 12:38:40 |
| maralorn | I wonder whether my problem also has to do with the wrong builder attribution. | 12:44:56 |
| maralorn | Well, deleted my log and: | 12:45:25 |
| maralorn | 
Download image.png | 12:45:28 |
| maralorn | fucking hell … | 12:45:33 |
| maralorn | File’s stale again … | 13:10:49 |
| maralorn | Well, at least now we know it’s not a bug in the file locking library. 🤣 | 13:11:15 |
| hexa | huh | 15:20:40 |
| 9 Mar 2025 |
|  Anton (he/him) joined the room. | 15:33:07 |
| 13 Mar 2025 |
|  Inayet joined the room. | 09:20:20 |
| 15 Mar 2025 |
|  isabel changed their profile picture. | 14:46:56 |
| 16 Mar 2025 |
| isabel changed their profile picture. | 17:39:58 |
| 17 Mar 2025 |
|  egrieco joined the room. | 06:48:00 |
| 27 Mar 2025 |
|  Helen joined the room. | 19:09:42 |
| Helen | Hello! The readme says that nom caches build times in this particular file "$XDG_CACHE_HOME/nix-output-monitor/build-reports.csv.", but I am not seeing this on my own machine. I am using M1 Mac. I've tried creating the directory manually in case that was the issue. Is there any other setup I need to do? | 19:10:53 |
| Helen | I would also like to ask if there's already a way to get all of nom's visual output into a txt file! | 19:12:17 |
| maralorn | Hey, Helen. I admit I have little experience with macs. In principle nom creates the directory by itself. | 20:59:33 |
| maralorn | Sadly there have been issues with the build times cache for years.^^ | 21:01:02 |
| maralorn | I am not sure what you mean by "getting all of nom’s visual output into a txt file". The problem is that nom emits a lot of terminal control codes, so that wouldn’t be very helpful. | 21:02:15 |
| maralorn | Ah, do you mean to basically keep a file up-to-date with the current summary? | 21:02:38 |
| maralorn | That is not implemented but sounds possible. But I wonder about the use case. | 21:03:25 |
