-
Notifications
You must be signed in to change notification settings - Fork 2
confusing outputs from nix flake shellHook
#4
Comments
Line 42 in 3e60a33
this line is being executed before
Re-running I guess an easy fix would be to simply suppress the error logs coming out of - blockcount=$(btc getblockcount) || { blockcount=-1; }
+ blockcount=$(btc getblockcount 2>/dev/null) || { blockcount=-1; } That would avoid confusing the user with a false alarm. |
Line 51 in 3e60a33
This line is generating the following error log:
Running
I still don't have any concrete suggestion on how to fix this. |
Line 56 in 3e60a33
This line is generating the following error log:
Running - ln_1_info=$(ln1 getinfo) || { ln_1_info=-1; }
+ ln_1_info=$(ln1 getinfo 2>/dev/null) || { ln_1_info=-1; } The same could also be applied to the |
shellHook
Hey, yes thanks for this you make some good points. I'll implement your suggestions to clean up the flake a bit. |
I'm running a x86-64 VM with a fresh NixOS 23.11.6359.53a2c32bc66f (Tapir)
The
shellHook
insideflake.nix
generates some confusing outputs:The text was updated successfully, but these errors were encountered: