nix-output-monitor
nix-output-monitor copied to clipboard
maralorn
Pipe your nix-build output through the nix-output-monitor a.k.a nom to get additional information while building.
An example would be having to build two version of nss, one for i686-linux and one for x86_64-linux, which happens when you're building wine-wow. It would be neat to have...
The biggest regression from using plain nix is that we don't have tab completion anymore. Do we have someone who is familiar with that kind of thing to make `nom-build`...
At the beginning of this project I didn‘t aim at the software quality that seems warranted by now. Hopefully with more documentation others will have it easier to contribute.
nom is not super efficient right now. I can think of multiple places where this might be happening, but I am effectively flying blind. A benchmarking setup would be super...
When the time taken by previous builds of some of the dependencies is known, would it be possible to display the sum? It can be understood as a lower bound...
Tested by deploying the config on an aarch64-linux without an x86_64-linux remote builders (in fact without any remote builders at all).
Hey, so I will try to explain the exact issue but I don't really know how to nail this down any further. My use case is pretty much a shell...
Output is spammed with `@nix {"action":"start"...` and seems to miss a lot of steps. 
When piping both stdout and stderr to nom, nom doesn't print back the trace messages: ``` $ nix build --no-eval-cache /home/ayats/Documents/dotfiles#nixosConfigurations."hermes".config.system.build.toplevel trace: nix-2.18.1 reached desired version 2.14.0 trace: warning: The...
