all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 33280@debbugs.gnu.org
Subject: bug#33280: Guix weather does not error nicely with 502 errors from hydra
Date: Tue, 06 Nov 2018 15:23:31 +0100	[thread overview]
Message-ID: <871s7y1dzw.fsf@gnu.org> (raw)
In-Reply-To: <87h8gvnski.fsf@netris.org> (Mark H. Weaver's message of "Mon, 05 Nov 2018 16:05:06 -0500")

Hi,

Mark H Weaver <mhw@netris.org> skribis:

> swedebugia <swedebugia@riseup.net> writes:
>
>> I did not change the default substitute-urls in 0.15
>>
>> This is probably low priority.
>>
>> sdb@komputilo ~$ guix weather
>> computing 7,850 package derivations for x86_64-linux...
>> looking for 8,167 store items on https://mirror.hydra.gnu.org...
>> guix weather: warning: while fetching
>> 'https://mirror.hydra.gnu.org/nix-cache-info': 502 ("Bad Gateway")
>> guix weather: warning: ignoring substitute server at
>> '"https://mirror.hydra.gnu.org"'
>> https://mirror.hydra.gnu.org
>>   .0% substitutes available (0 out of 8,167)
>>   unknown substitute sizes
>>   0.0 MiB on disk (uncompressed)
>>   0.000 seconds per request (2.7 seconds in total)
>>   3,081.9 requests per second
>>   (continuous integration information unavailable)
>>
>> We should omit everything after the first warning I think.
>
> At the time you wrote this, hydra.gnu.org was partially back up, but
> with several of the important daemons not yet started.  I've since
> started the daemons, so it might work now.

Also, I would argue that this behavior (printing a warning and ignoring
the faulty server) is good.  I can’t think of a better way to handle
this situation.

Thoughts?

Ludo’.

  reply	other threads:[~2018-11-06 14:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 20:23 bug#33280: Guix weather does not error nicely with 502 errors from hydra swedebugia
2018-11-05 21:05 ` Mark H Weaver
2018-11-06 14:23   ` Ludovic Courtès [this message]
2018-11-06 19:07     ` swedebugia
2018-11-07 21:01       ` Ludovic Courtès

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=871s7y1dzw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33280@debbugs.gnu.org \
    --cc=mhw@netris.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.