nix-output-monitor | 110 Members | |
| https://github.com/maralorn/nix-output-monitor | 37 Servers |
| Sender | Message | Time |
|---|---|---|
| 14 Mar 2026 | ||
| 19:28:40 | ||
| 21:22:06 | ||
| 15 Mar 2026 | ||
| 00:32:20 | ||
| 02:38:54 | |
| it's infuriating when the error is cut off | 02:39:04 | |
| Huh | 09:10:27 | |
| The question is why doesn't the error appear in the logs? | 09:10:52 | |
| Very weird. | 09:12:03 | |
| The message says "last 25 log lines" and then it shows 23 lines? | 09:13:27 | |
| I don't even know how nom could be screwing that up. | 09:14:41 | |
| Funny thing: We have users complaining that we show errors twice: once in the logs and once in the footer. But here the error doesn't appear in the logs at all. | 09:16:40 | |
| Nom definitely does weird things to the output | 17:38:16 | |
| I've seen it, I dunno, clear output of preceding nom run | 17:39:03 | |
| I ran nom twice, and afterwards, my next to last prompt had a non-nom command on it | 17:40:05 | |
| Happened multiple times | 17:40:16 | |
| Well, nom tries to remember how many lines have been written and need to be cleared. It is definitely possible that something invalidates the internal computation. | 18:30:27 | |
| Other terminal applications mainly prevent this from happening by switching the terminal mode and completely owning the buffer, which I want to avoid with nom so that you normally get a valid log. | 18:32:32 | |
| why does it need to clear things in the first place? | 18:47:29 | |
| what if it was like a tmux thing | 18:47:48 | |
| with normal log in one pane/terminal and the monitoring in another | 18:48:23 | |
| my main reason for not always using nom is that the control characters and redrawing clutter the resulting log so it's harder to inspect logs after the build | 18:49:13 | |
| I can imagine something like
| 18:51:11 | |
| I am not aware of a solution where nom can do "a tmux thing" an produce a viable scrollable log in the terminal which is readable after exit. | 19:44:29 | |
| But maybe that's a misconception. Maybe we can figure out how to do that. | 19:48:02 | |
| 20:27:59 | ||
| 20:54:42 | ||
| 20:54:56 | ||
| 16 Mar 2026 | ||
| huh nom swallows traces as well | 22:40:14 | |
| 22:40:37 | |
or, if I leave it running
| 22:41:42 | |