TTobias Geerinckx-Rice wrote on 2 Mar 2021 17:32
(address . email@example.com)
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
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
Toggle snippet (37 lines)
~ $ 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'...
2164:12 10 (run-guix-command _ . _)
1736:10 9 (with-exception-handler _ _ #:unwind? _
1731:15 8 (with-exception-handler #<procedure 7fe8a173d7e0 at
ice-9/boot-9.scm:1815:7 (exn)> _ #:unwind? _ …)
546:9 7 (_)
569:23 6 (every* #<procedure 7fe875fdd4e0 at
guix/scripts/weather.scm:546:17 (server)> _)
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 _>
411:23 2 (lookup-narinfos _ _ #:open-connection _)
371:26 1 (fetch-narinfos _ _ #:open-connection _)
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)'.