unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 46877@debbugs.gnu.org
Subject: bug#46877: Guix assumes ideal network exists, does not
Date: Tue, 02 Mar 2021 17:32:50 +0100	[thread overview]
Message-ID: <87eegxms7h.fsf@nckx> (raw)

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

Guixfriends,

Errors like the one below are omnipresent.  It's a problem.

Expecting an ever-increasing (16k+?) number of requests to finish 
flawlessly or aborting a very long (20+ minutes here) process is 
doomed.

We don't seem to have a plan forward (I include myself!).  Looking 
at other package managers, a blunt ‘retry a finite number of 
times’ seems common.  Guix's ‘pretend that "transient" is a magic 
powerword’ approach less so.

What do people think?  Does the heavy pipelining complicate 
matters?

--8<---------------cut here---------------start------------->8---
~ $ guix weather --substitute-urls=https://guix.tobias.gr
computing 16,745 package derivations for x86_64-linux...
looking for 18,127 store items on https://guix.tobias.gr...
updating substitutes from 'https://guix.tobias.gr'... 
41.6%Backtrace:
          11 (primitive-load 
          "/home/nckx/.config/guix/current/bin/guix")
In guix/ui.scm:
  2164:12 10 (run-guix-command _ . _)
In ice-9/boot-9.scm:
  1736:10  9 (with-exception-handler _ _ #:unwind? _ 
  #:unwind-for-type _)
  1731:15  8 (with-exception-handler #<procedure 7fe8a173d7e0 at 
  ice-9/boot-9.scm:1815:7 (exn)> _ #:unwind? _ …)
In guix/scripts/weather.scm:
    546:9  7 (_)
In guix/build/utils.scm:
   569:23  6 (every* #<procedure 7fe875fdd4e0 at 
   guix/scripts/weather.scm:546:17 (server)> _)
In guix/scripts/weather.scm:
   547:19  5 (_ "https://guix.tobias.gr")
   116:17  4 (report-server-coverage _ _ #:display-missing? _)
In unknown file:
           3 (_ #<procedure 7fe86e3cbbe0 at 
           guix/scripts/weather.scm:184:2 ()> #<procedure list _> 
           . #w())
In guix/scripts/substitute.scm:
   411:23  2 (lookup-narinfos _ _ #:open-connection _)
   371:26  1 (fetch-narinfos _ _ #:open-connection _)
In ice-9/boot-9.scm:
  1669:16  0 (raise-exception _ #:continuable? _)

ice-9/boot-9.scm:1669:16: In procedure raise-exception:
Throw to key `gnutls-error' with args `(#<gnutls-error-enum Error 
in the pull function.> read_from_session_record_port)'.
--8<---------------cut here---------------end--------------->8---

Kind regards,

T G-R

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

             reply	other threads:[~2021-03-02 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 16:32 Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2021-03-02 19:55 ` bug#46877: Guix assumes ideal network exists, does not Leo Famulari
2021-03-02 20:00 ` zimoun
2021-03-02 20:18   ` zimoun
2021-03-10 11:17 ` Ludovic Courtès
2021-03-10 22:04   ` zimoun

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=87eegxms7h.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=46877@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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).