aboutsummaryrefslogtreecommitdiff
path: root/scripts/nix-reduce-build.in
diff options
context:
space:
mode:
authorFlorian Klink <flokli@flokli.de>2019-05-06 22:23:15 +0200
committerFlorian Klink <flokli@flokli.de>2019-05-11 12:34:39 +0200
commit6ade7ec022c836b7d1f9bd06be45e2c07835ec8c (patch)
treeefbe004bd8a64e3a04b35af416c03f0564285b7e /scripts/nix-reduce-build.in
parentf9a2ea44867cd1dbb408bca4df0ced806137b7f7 (diff)
progress-bar: hide expected if expected is 0 (unknown)
Sometimes, "expected" can be "0", but in fact means "unknown". This is for example the case when downloading a file while the http server doesn't send the `Content-Length` header, like when running `nix build` pointing to a nixpkgs checkout streamed from GitHub: ⇒ nix build -f https://github.com/NixOS/nixpkgs/archive/master.tar.gz hello [1.8/0.0 MiB DL] downloading 'https://github.com/NixOS/nixpkgs/archive/master.tar.gz' In that case, don't show that weird progress bar, but only the (slowly increasing) downloaded size ("done"). ⇒ nix build -f https://github.com/NixOS/nixpkgs/archive/master.tar.gz hello [1.8 MiB DL] downloading 'https://github.com/NixOS/nixpkgs/archive/master.tar.gz' This commit also updates fmt calls with three numbers (when something is currently 'running' too) - I'm not sure if this can be provoked, but showing "0" as expected doesn't make any sense, as we're obviously doing more than nothing.
Diffstat (limited to 'scripts/nix-reduce-build.in')
0 files changed, 0 insertions, 0 deletions