nix-output-monitor
nix-output-monitor copied to clipboard
nom-build swallows errors
Assumption is that nom exits too fast to print the error the first time.

Another instance which shows it doesn't swallow them completely, but only the first 3 lines:
Expected (w/o nom being used):
❯ nix run github:paisano-nix/tui //app/deployments/dev-preview:explore
error:
─────┬─────────────────────────────────────────────────────────────────────────
🔥 │ Prohibitive Dirty Git Tree !
─────┼─────────────────────────────────────────────────────────────────────────
📝 │ Will not render manifests from a dirty tree.
│ Otherwise we cannot keep good track of deployment history.
│
─────┴─────────────────────────────────────────────────────────────────────────
Nom:
❯ nix run github:paisano-nix/tui //app/deployments/dev-preview:explore
─────┼─────────────────────────────────────────────────────────────────────────
📝 │ Will not render manifests from a dirty tree.
│ Otherwise we cannot keep good track of deployment history.
│
─────┴─────────────────────────────────────────────────────────────────────────
EDIT:
(wow what a remarkable pace of development, recently! :rocket:)
Just the latest version of NOM shows the full error:
❯ nix run github:paisano-nix/tui //app/deployments/dev-preview:explore
─────┼─────────────────────────────────────────────────────────────────────────
📝 │ Will not render manifests from a dirty tree.
│ Otherwise we cannot keep good track of deployment history.
─────┴─────────────────────────────────────────────────────────────────────────
┏━ 1 Errors:
┃ error:
┃ ─────┬─────────────────────────────────────────────────────────────────────────
┃ 🔥 │ Prohibitive Dirty Git Tree !
┃ ─────┼─────────────────────────────────────────────────────────────────────────
┃ 📝 │ Will not render manifests from a dirty tree.
┃ │ Otherwise we cannot keep good track of deployment history.
┃ ─────┴─────────────────────────────────────────────────────────────────────────
┣━━━
┗━ ∑︎ ⚠︎ Exited with 1 errors reported by nix at 19:10:25 after 1s
(albeit somewhat twice, so this issue is attenuated)