unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 48376@debbugs.gnu.org
Subject: bug#48376: Failure in "guix pull"
Date: Mon, 17 May 2021 16:37:41 -0400	[thread overview]
Message-ID: <874kf1nlka.fsf@gmail.com> (raw)
In-Reply-To: <m14kf3axnc.fsf@ordinateur-de-catherine--konrad.home> (Konrad Hinsen's message of "Sun, 16 May 2021 10:30:31 +0200")

Hi Konrad,

Konrad Hinsen <konrad.hinsen@fastmail.net> writes:

> Hi Maxim,
>
> Thanks for your reply!
>
>> Indeed.  I note that the error message that leads to a request to the
>> bug report mention it could be due to a network failure, which could
>> explain the transient nature of the problem we see here.
>>
>> Had you tried multiple times in a row with the same failure on that
>> commit?
>
> Yes, I tried again later on two different machines, without any problem.
>
> The reason I submitted a bug report is because Guix told me so. I
> assumed that even if the root cause was a network issue, something had
> then happened that shouldn't happen. If that's not the case, then the
> error message should be improved. A minimal improvement would be to say
> "Please report unless you see a comment about networking issues above.".

I agree!  We don't want people to send bug reports every time their
network is flaky, if this is indeed what has happened.  Would you be
interested at surveying if that's the case in the current code?  Perhaps
the right change would then become apparent.

Thank you,

Maxim




  reply	other threads:[~2021-05-17 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 10:15 bug#48376: Failure in "guix pull" Konrad Hinsen
2021-05-12 11:54 ` Konrad Hinsen
2021-05-15  2:10   ` Maxim Cournoyer
2021-05-16  8:30     ` Konrad Hinsen
2021-05-17 20:37       ` Maxim Cournoyer [this message]
2021-05-24 16:07         ` Konrad Hinsen

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=874kf1nlka.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=48376@debbugs.gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).