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 # _ #:unwind? _ …) In guix/scripts/weather.scm: 546:9 7 (_) In guix/build/utils.scm: 569:23 6 (every* # _) In guix/scripts/weather.scm: 547:19 5 (_ "https://guix.tobias.gr") 116:17 4 (report-server-coverage _ _ #:display-missing? _) In unknown file: 3 (_ # # . #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 `(# read_from_session_record_port)'. --8<---------------cut here---------------end--------------->8--- Kind regards, T G-R