unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 63794@debbugs.gnu.org
Subject: bug#63794: Bad error reporting in case of 404 during downloading
Date: Tue, 30 May 2023 14:13:42 +0100	[thread overview]
Message-ID: <87cz2ihsfy.fsf@cbaines.net> (raw)
In-Reply-To: <f4b6f127-9461-c8f0-b6d8-baef96639394@telenet.be>

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]


Maxime Devos <maximedevos@telenet.be> writes:

> Problems:
>   * The server not having a file is not an exceptional situation;
>     it should just skip this server or just report that there
>     is no available location for this resource instead of
>     a backtrace.
>
>   * It claims ‘corrupt input while restoring ...’, but it isn't
>     corrupt -- non-existence is not a form of corruption.
>
>   * ‘1.46Gi’ should be ‘1.46GiB’ or ‘1.46GiB/s’ -- Gi is just a prefix,
>     it's missing a unit.

I think the key bits here might be a duplicate of #63634

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  parent reply	other threads:[~2023-05-30 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 22:05 bug#63794: Bad error reporting in case of 404 during downloading Maxime Devos
2023-05-30  6:27 ` bug#63794: N. Y.
2023-05-30 10:05   ` bug#63794: Christopher Baines
2023-05-31  9:02     ` bug#63794: Simon Tournier
2023-05-30  9:06 ` bug#63794: Bad error reporting in case of 404 during downloading Zain Jabbar
2023-05-30 13:13 ` Christopher Baines [this message]
2023-05-30 14:41   ` Maxime Devos
2023-06-08 20:50     ` Maxime Devos
     [not found] ` <handler.63794.B.16853979367295.ack@debbugs.gnu.org>
2023-05-30 13:25   ` bug#63794: Acknowledgement (Bad error reporting in case of 404 during downloading) Maxime Devos
2023-05-30 13:29     ` Christopher Baines
2023-05-30 15:53 ` bug#63794: Bad error reporting in case of 404 during downloading Simon Tournier

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=87cz2ihsfy.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=63794@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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).