GNU bug report logs - #65549
Issue during "guix pull"

Previous Next

Package: guix;

Reported by: Philip Kaludercic <philipk <at> posteo.net>

Date: Sat, 26 Aug 2023 08:54:02 UTC

Severity: normal

Done: Simon Tournier <zimon.toutoune <at> gmail.com>

Full log


Message #14 received at 65549 <at> debbugs.gnu.org (full text, mbox):

From: Philip Kaludercic <philipk <at> posteo.net>
To: Simon Tournier <zimon.toutoune <at> gmail.com>
Cc: Josselin Poiret <dev <at> jpoiret.xyz>, 65549 <at> debbugs.gnu.org
Subject: Re: bug#65549: Issue during "guix pull"
Date: Tue, 29 Aug 2023 12:11:31 +0000
Simon Tournier <zimon.toutoune <at> gmail.com> writes:

> Hi,
>
> On Sun, 27 Aug 2023 at 09:28, Josselin Poiret via Bug reports for GNU Guix <bug-guix <at> gnu.org> wrote:
>
>> Philip Kaludercic <philipk <at> posteo.net> writes:
>>
>>> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
>>> ERROR:
>>>   1. &http-get-error:
>>>       uri: #<<uri> scheme: https userinfo: #f host: "ci.guix.gnu.org" port: #f path: "/nar/lzip/i4c6yd0n7yhw2qi5217z62zb9n023dk7-automake-1.16.5" query: #f fragment: #f>
>>>       code: 504
>>>       reason: "Gateway Time-out"
>>
>> It looks like you have connectivity issues with ci.guix.gnu.org.  You
>> might want to retry, or enable other mirrors for substitutes instead,
>> since ci.guix.gnu.org blocks some territories (not because of Guix
>> policy, but rather because of where the server is hosted).
>
> Well, it’s weird that many people have often connectivity issues with
> ci.guix.gnu.org.  I mean, yes a retry usually makes it pass but as
> reported in this thread:
>
>     collection of “guix pull“ bug reports
>     Simon Tournier <zimon.toutoune <at> gmail.com>
>     Wed, 23 Aug 2023 18:17:20 +0200
>     id:86jztl20of.fsf <at> gmail.com
>     https://yhetil.org/guix/86jztl20of.fsf <at> gmail.com
>     https://lists.gnu.org/archive/html/guix-devel/2023-08
>
> all these failures with “guix pull“ look like the symptom with something
> unexpected on server side.  Although obviously we can tweak on client
> side for some automatic retries.
>
> These transient failures are very hard to tackle because they are
> transient. :-)

Is it not possible to detect connectivity issues and print a regular
error message, instead of instructing the user to report a bug?

>
> Cheers,
> simon




This bug report was last modified 1 day ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.