“guix pull” should show a progress bar for channel updates

  • Done
  • quality assurance status badge
Details
3 participants
  • Ludovic Courtès
  • Ricardo Wurmus
  • zimoun
Owner
unassigned
Submitted by
Ricardo Wurmus
Severity
important
Merged with
R
R
Ricardo Wurmus wrote on 19 May 2020 23:30
“guix pull” should show a progress bar for channel updates
(address . bug-guix@gnu.org)
87imgrfw9i.fsf@elephly.net
When I run “guix pull” (or “guix time-machine”) I see this message

Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...

followed by disconcerting silence. I can’t tell if it’s doing
something, nor can I see what the progress is.

Would be nice to have a progress bar or at least a spinner.

--
Ricardo
Z
Z
zimoun wrote on 21 May 2020 13:00
Re: bug#41409: “guix pull” should show a progres s bar for channel updates
(name . Ricardo Wurmus)(address . rekado@elephly.net)(address . 41409@debbugs.gnu.org)
CAJ3okZ1LnAsiKyqHRUDX5P=petQSj-5K19JhtPXHbDm9=jfpSQ@mail.gmail.com
Hi Ricardo,

On Tue, 19 May 2020 at 23:31, Ricardo Wurmus <rekado@elephly.net> wrote:

Toggle quote (7 lines)
> When I run “guix pull” (or “guix time-machine”) I see this message
>
> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>
> followed by disconcerting silence. I can’t tell if it’s doing
> something, nor can I see what the progress is.

Most of the time is fetching from network so if you have a good
network connection, this step is not long enough to be disconcerting.
:-)

In addition to this whislist, it appears to me the same for "Computing
Guix derivation", even there is something moving.


All the best,
simon
R
R
Ricardo Wurmus wrote on 21 May 2020 22:09
Re: bug#41409: “guix pull” should show a progress bar for channel updates
(name . zimoun)(address . zimon.toutoune@gmail.com)(address . 41409@debbugs.gnu.org)
87367tdp8u.fsf@elephly.net
zimoun <zimon.toutoune@gmail.com> writes:

Toggle quote (13 lines)
> On Tue, 19 May 2020 at 23:31, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> When I run “guix pull” (or “guix time-machine”) I see this message
>>
>> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>>
>> followed by disconcerting silence. I can’t tell if it’s doing
>> something, nor can I see what the progress is.
>
> Most of the time is fetching from network so if you have a good
> network connection, this step is not long enough to be disconcerting.
> :-)

It can take several seconds or even over a few minutes when fetching
from multiple channels. For what it’s worth I got annoyed waiting for
“guix pull” on ci.guix.gnu.org, which has a pretty decent network
connection (even though users on the outside cannot see it this way due
to the firewall).

--
Ricardo
Z
Z
zimoun wrote on 22 May 2020 00:29
Re: bug#41409: “guix pull” should show a progres s bar for channel updates
(name . Ricardo Wurmus)(address . rekado@elephly.net)(address . 41409@debbugs.gnu.org)
CAJ3okZ34VFPPw3dJ1dxNio20_FrM350XJf8Dw3wj4_PaoB9jDA@mail.gmail.com
On Thu, 21 May 2020 at 22:09, Ricardo Wurmus <rekado@elephly.net> wrote:

Toggle quote (6 lines)
> It can take several seconds or even over a few minutes when fetching
> from multiple channels. For what it’s worth I got annoyed waiting for
> “guix pull” on ci.guix.gnu.org, which has a pretty decent network
> connection (even though users on the outside cannot see it this way due
> to the firewall).

Wow! Few minutes. To me, each channel (Gitlab, GitHub, etc.) takes a
couple of seconds -- even with a poor Wifi connection -- and the
longest is Guix from Savannah: and "slow" as everything under gnu.org.
I feel much more frustrated by "Computing Guix derivation" which takes
ages on my machine and I never know if the computations are at 20% or
80% or whatever.
And I never pull on my laptop the current HEAD of master otherwise I
am waiting between 10 and 30 minutes building all the derivations
because they are not substituable yet; well I pull 1 or 2 weeks
behind.

Well, a spinner for the Git updating part could improve use cases:
first pull, long period between 2 pulls, firewall, etc..
On the other hand, an European mirror of guix.git could help too, IMHO.

Cheers,
simon
L
L
Ludovic Courtès wrote on 24 May 2020 23:17
Re: bug#41409: “guix pull” should show a progress bar for channel updates
(name . Ricardo Wurmus)(address . rekado@elephly.net)(address . 41409@debbugs.gnu.org)
875zclyqve.fsf@gnu.org
Hi,

Ricardo Wurmus <rekado@elephly.net> skribis:

Toggle quote (7 lines)
> When I run “guix pull” (or “guix time-machine”) I see this message
>
> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>
> followed by disconcerting silence. I can’t tell if it’s doing
> something, nor can I see what the progress is.

For the record, the main missing piece is in Guile-Git, which does not
yet provide bindings to the progress-report thingie for fetch
operations.

Ludo’.
L
L
Ludovic Courtès wrote on 2 Jul 2020 00:15
control message for bug #39260
(address . control@debbugs.gnu.org)
87366ayj9j.fsf@gnu.org
merge 39260 41409
quit
L
L
Ludovic Courtès wrote on 2 Jul 2020 00:15
(address . control@debbugs.gnu.org)
871rluyj9e.fsf@gnu.org
severity 39260 important
quit
L
L
Ludovic Courtès wrote on 5 Oct 2020 09:45
Re: bug#41409: “guix pull” should show a progress bar for channel updates
(name . Ricardo Wurmus)(address . rekado@elephly.net)
874kn96rq3.fsf@gnu.org
Hi,

Ludovic Courtès <ludo@gnu.org> skribis:

Toggle quote (13 lines)
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> When I run “guix pull” (or “guix time-machine”) I see this message
>>
>> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>>
>> followed by disconcerting silence. I can’t tell if it’s doing
>> something, nor can I see what the progress is.
>
> For the record, the main missing piece is in Guile-Git, which does not
> yet provide bindings to the progress-report thingie for fetch
> operations.

I’ve added support for the ‘transfer-progress’ callback in Guile-Git:


However, there’s an (unrelated) issue with libgit2 meaning that
Guile-Git is not in a releasable state yet:


Ludo’.
L
L
Ludovic Courtès wrote on 12 Oct 2020 23:30
(name . Ricardo Wurmus)(address . rekado@elephly.net)
87lfgbm8sm.fsf@gnu.org
Ludovic Courtès <ludo@gnu.org> skribis:

Toggle quote (19 lines)
> Ludovic Courtès <ludo@gnu.org> skribis:
>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> When I run “guix pull” (or “guix time-machine”) I see this message
>>>
>>> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>>>
>>> followed by disconcerting silence. I can’t tell if it’s doing
>>> something, nor can I see what the progress is.
>>
>> For the record, the main missing piece is in Guile-Git, which does not
>> yet provide bindings to the progress-report thingie for fetch
>> operations.
>
> I’ve added support for the ‘transfer-progress’ callback in Guile-Git:
>
> https://gitlab.com/guile-git/guile-git/-/commit/7a3d97a72e7907213241f62d3bac926361f50f95

And now the Guix side of it:


Toggle quote (5 lines)
> However, there’s an (unrelated) issue with libgit2 meaning that
> Guile-Git is not in a releasable state yet:
>
> https://github.com/libgit2/libgit2/issues/5650

It’s a libgit2 bug but not a showstopper after all.

Ludo’.
L
L
Ludovic Courtès wrote on 26 Oct 2020 23:52
Re: bug#39260: bug#41409: “guix pull” should show a progress bar for channel updates
(name . Ricardo Wurmus)(address . rekado@elephly.net)
87pn548usc.fsf@gnu.org
Ludovic Courtès <ludo@gnu.org> skribis:

Toggle quote (4 lines)
> And now the Guix side of it:
>
> https://issues.guix.gnu.org/43968

Merged in 298f9d29d6c26e408a90d08d147d926aa6f81ab3, closing!

Ludo’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 41409@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 41409
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch