unofficial mirror of 
 help / color / mirror / code / Atom feed
From: Maxime Devos <>
Subject: bug#56980: "corrupt input while restoring [...] from [...]" when it's just a network timeout
Date: Thu, 4 Aug 2022 18:07:40 +0200	[thread overview]
Message-ID: <> (raw)

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



I recently got the following output:

> substitutie van 
> /gnu/store/yzswm5i0l0rvc01lfkb5z5lz4a85p6z8-rust-proc-macro-error-attr-1.0.4-lib 
> is klaar
> /gnu/store/zi1yc0fmq7yi564sv23h13qc97s445bb-rust-prost-derive-0.9.0-lib 
> vervangen...
> guix substitute: waarschuwing: tijdens het binnenhalen van 
> guix substitute: waarschuwing: probeer ‘--no-substitutes’ als het 
> probleem hardnekkig is
> guix substitute: fout: connect*: Verbinding is verlopen
> vervanging van 
> /gnu/store/6p12gnwvfmqbfhdhcak71dcwkgd10ir7-rust-codespan-reporting-0.11.0-lib 
> mislukt
> guix build: fout: beschadigde invoer tijdens het terugplaatsen van het 
> archief uit #<closed: file 7f80ab995e00>


guix substitute: warning: while fetching ~a: server is somewhat slow~%
guix substitute: warning: try `--no-substitutes' if the problem persists~%
guix substitute: error: connect*: Connection timed out
substitution of ~a failed
guix build: error: corrupt input while restoring archive from ~s~%"

Two remarks:

  * I don't think a timeout counts as "corrupted", "corrupted" sounds
    like a bit flip or such happened or that there is a bug in the nix
    archive code that causes the archive to be (non-deterministically?)
  * The name of the procedure 'connect*' sounds like an implementation
    detail, could the error message be changed to plainly state it's
    just a timeout?

Maybe a duplicate of <>.

Possibly the same issue as <>?


[-- Attachment # Type: text/html, Size: 2645 bytes --]

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

                 reply	other threads:[~2022-08-04 16:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  List information:

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

  git send-email \ \ \ \ \

* 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

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).