all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: guix-devel <guix-devel@gnu.org>
Subject: Reducing default verbosity
Date: Tue, 5 Dec 2017 14:33:01 +0100	[thread overview]
Message-ID: <87vahlti42.fsf@mdc-berlin.de> (raw)

Hi Guix,

for the release after 0.14.0 I’d like us to implement changes to the
default verbosity of Guix commands.

Here are a few things that I think would make for better defaults:

* Reduce package downloads from three lines to one line.  The
  “Downloading URL” line is only important when things go wrong.
* Reduce precision in percentages.  The extra digit and the period
  contribute to visual noise.
* Widen progress bar, so that it changes more quickly.

  Before:
  
    Downloading https://berlin.guixsd.org/nar/gzip/r43434523452345…-zlib-1.2.11…
     zlib-1.2.11    151KiB      12.6MiB/s  00:00 [###############] 100.0%

    Downloading https://berlin.guixsd.org/nar/gzip/rlol…-libpng-1.6.29…
     libpng-1.6.29  377KiB      10.6MiB/s  00:00 [#############  ]  90.0%

  After:

    zlib-1.2.11     151KiB  00:00 [##############################] 100%  12.6MiB/s
    libpng-1.6.29   377KiB  00:00 [#########################     ]  90%  10.6MiB/s

* Redirect all build output to log files; as we can’t generally estimate
  progress I’d use a spinner and maybe display the name of the current
  build phase and the number of build phases that are left.

  Building openldap-2.4.45 (2/6)  [‐----->-----------------------]
  Building openldap-2.4.45 (2/6)  [‐-------------->--------------]
  Building openldap-2.4.45 (3/6)  [‐----------------------->-----]
  Building openldap-2.4.45 (4/6)  [‐-----------------<-----------]
  Building openldap-2.4.45 (4/6)  [-------------<----------------]

  There are some pretty single character unicode spinners here:
    https://github.com/pmonks/spinner/blob/master/src/spinner/core.clj

* Remove double messages that are printed by the daemon and the Guix
  client, e.g. hash mismatches.  Here’s an example of this:

--8<---------------cut here---------------start------------->8---
rekado in ~: guix build guile-sjson
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
@ build-started /gnu/store/f4a56cwcb45mkd8vgpjprx06rs4vqhws-sjson-0.2.1.tar.gz.drv - x86_64-linux /var/log/guix/drvs/f4//a56cwcb45mkd8vgpjprx06rs4vqhws-sjson-0.2.1.tar.gz.drv.bz2

Starting download of /gnu/store/59k6bgh00312a0vnha65hzs45b6z6vpq-sjson-0.2.1.tar.gz
From https://dustycloud.org/misc/sjson-0.2.1.tar.gz...
 ....1.tar.gz  90KiB                757KiB/s 00:00 [####################] 100.0%
sha256 hash mismatch for output path `/gnu/store/59k6bgh00312a0vnha65hzs45b6z6vpq-sjson-0.2.1.tar.gz'
  expected: 0mzmapln79vv10qxaggz9qwcdbag3jnrj19xx8bgkmxss8h03sv3
  actual:   1mzmapln79vv10qxaggz9qwcdbag3jnrj19xx8bgkmxss8h03sv3
@ build-failed /gnu/store/f4a56cwcb45mkd8vgpjprx06rs4vqhws-sjson-0.2.1.tar.gz.drv - 1 sha256 hash mismatch for output path `/gnu/store/59k6bgh00312a0vnha65hzs45b6z6vpq-sjson-0.2.1.tar.gz'
  expected: 0mzmapln79vv10qxaggz9qwcdbag3jnrj19xx8bgkmxss8h03sv3
  actual:   1mzmapln79vv10qxaggz9qwcdbag3jnrj19xx8bgkmxss8h03sv3
cannot build derivation `/gnu/store/l14gbyb0n7wb2j1ff7ixqah93afzjxia-guile-sjson-0.2.1.drv': 1 dependencies couldn't be built
guix build: error: build failed: build of `/gnu/store/l14gbyb0n7wb2j1ff7ixqah93afzjxia-guile-sjson-0.2.1.drv' failed
rekado in ~: 
--8<---------------cut here---------------end--------------->8---

What do you think?

-- 
Ricardo

             reply	other threads:[~2017-12-05 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 13:33 Ricardo Wurmus [this message]
2017-12-05 14:04 ` Reducing default verbosity Danny Milosavljevic
2017-12-06 10:20   ` Ludovic Courtès
2017-12-06  1:47 ` Leo Famulari
2017-12-06 10:21   ` Ludovic Courtès
2017-12-06 17:03     ` Hartmut Goebel
2017-12-06 17:01 ` Hartmut Goebel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vahlti42.fsf@mdc-berlin.de \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.