From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#33151: 'guix substitute' returns a 504 error without trying to use other servers Date: Mon, 05 Nov 2018 22:33:16 +0100 Message-ID: <87zhunw6oz.fsf@gnu.org> References: <87h8haf3ft.fsf@lassieur.org> <87h8h8d2c6.fsf@gnu.org> <87muqnn6ck.fsf@lassieur.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34522) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gJmW7-0003Oj-Li for bug-guix@gnu.org; Mon, 05 Nov 2018 16:34:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gJmVW-0005a6-3z for bug-guix@gnu.org; Mon, 05 Nov 2018 16:34:02 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:59746) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gJmVV-0005a1-WD for bug-guix@gnu.org; Mon, 05 Nov 2018 16:34:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gJmVV-0003ym-SM for bug-guix@gnu.org; Mon, 05 Nov 2018 16:34:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87muqnn6ck.fsf@lassieur.org> ("=?UTF-8?Q?Cl=C3=A9ment?= Lassieur"'s message of "Mon, 05 Nov 2018 11:53:15 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: =?UTF-8?Q?Cl=C3=A9ment?= Lassieur Cc: 33151@debbugs.gnu.org Hello Cl=C3=A9ment, Cl=C3=A9ment Lassieur skribis: > I don't understand why you closed the bug report. Your explanation of > the bug makes sense, but it doesn't mean that it's fixed. > > I expect that when a substitute server is down, for whatever reason, > Guix should still work smoothly if there is another server set up. > > If you think there is no way to fix it, maybe the tag "wontfix" would be > more appropriate? No I think you=E2=80=99re right, I shouldn=E2=80=99t have closed it. I think my first thought was that the problem (narinfo available but corresponding nar missing) was mostly due to our peculiar nginx setup on mirror.hydra.gnu.org: this cannot happen under normal circumstances because =E2=80=98guix publish=E2=80=99 really honors the expiry it sets on = narinfos. That said, we could fix =E2=80=98process-substitution=E2=80=99 in (guix scr= ipts substitute) to try other nar URLs (if any) upon failure. IMO such a fix is not =E2=80=9Chigh-priority=E2=80=9D for the reason I gave= above, but OTOH it can be helpful to better cope with the sad reality of situations like the one we=E2=80=99re in. Thoughts? Thanks for the heads-up, and sorry for hitting the =E2=80=9Cclose=E2=80=9D = button too quickly! Ludo=E2=80=99.