Report forwarded
to ludo@gnu.org, 48903@debbugs.gnu.org, maxim.cournoyer@gmail.com, bug-guix@gnu.org: bug#49132; Package guix.
(Sun, 20 Jun 2021 11:09:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Maxime Devos <maximedevos@telenet.be>:
New bug report received and forwarded. Copy sent to ludo@gnu.org, 48903@debbugs.gnu.org, maxim.cournoyer@gmail.com, bug-guix@gnu.org.
(Sun, 20 Jun 2021 11:09:02 GMT) (full text, mbox, link).
Subject: Re: bug#49132: guix substitute: backtrace when the network is
disabled during substitution
Date: Tue, 22 Jun 2021 16:06:02 +0200
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> so I disabled & re-enabled wireless networking during the substitution
> and encountered a (to my knowledge) previously-unknown backtrace:
>
> $ while (echo substitute /gnu/store/44h13hn5zssfppz67vydxcf95qsc8qfw-libreoffice-6.4.7.2 /tmp/t && echo substitute /gnu/store/j0j7z6ckarjs9yi77sncszbmdgy38s70-guix-1.3.0-4.4985a42 /tmp/u) | guix
> substitute --substitute ; do chmod -R +w /tmp/t && rm -rf /tmp/t && chmod -R +w /tmp/u && rm -rf /tmp/u ; done
[...]
> In lzlib.scm:
> 501:4 9 (lzread! #<lz-decoder 7f0d0b7d5ef0> #<input: string 7f…> …)
> In unknown file:
> 8 (get-bytevector-n #<input: string 7f0d0b7d3e70> 65537)
> In guix/progress.scm:
> 368:31 7 (read! _ _ _)
> In unknown file:
> 6 (get-bytevector-n! #<input: string 7f0d0a15e4d0> # 0 #)
> In web/response.scm:
> 95:2 5 (read! _ _ _)
> In ice-9/boot-9.scm:
> 1685:16 4 (raise-exception _ #:continuable? _)
> 1685:16 3 (raise-exception _ #:continuable? _)
> 1780:13 2 (_ #<&compound-exception components: (#<&error> #<&irri…>)
> 1685:16 1 (raise-exception _ #:continuable? _)
> 1685:16 0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> Throw to key `bad-response' with args `("EOF while reading response body: ~a bytes of ~a" (26017808 37842870))'.
Ah indeed, this is poorly handled.
I’m not really sure how to address it. I/O ports are a nice abstraction
as it allows you to transparently read “streams” from any medium, but as
always, that also comes with opacity where the call site is not supposed
to know what kind of exceptions might be thrown deep down.
Thoughts?
Ludo’.
Severity set to 'important' from 'normal'
Request was from Ludovic Courtès <ludo@gnu.org>
to control@debbugs.gnu.org.
(Mon, 28 Jun 2021 21:16:01 GMT) (full text, mbox, link).
Information forwarded
to bug-guix@gnu.org: bug#49132; Package guix.
(Thu, 08 Jun 2023 21:18:02 GMT) (full text, mbox, link).
> Ah indeed, this is poorly handled.
>
> I’m not really sure how to address it. I/O ports are a nice abstraction
> as it allows you to transparently read “streams” from any medium, but as
> always, that also comes with opacity where the call site is not supposed
> to know what kind of exceptions might be thrown deep down.
>
> Thoughts?
About 'as always, [...]’: [citation needed]. AFAICT, nowhere does Guile
documentation state they they aren't supposed to know.
Also, that seems a bad supposition to me if it prevents fixing the bug.
I would just ignore that 'not supposed to’.
I think this supposition needs some adjustment in order to be practical:
guix/scripts/substitute.scm has opened the network connection (via
http-client), so guix/scripts/substitute.scm is responsible for the
connection (unless it delegates of course), so
guix/scripts/substitute.scm is supposed to know what to do about
exceptions involving that connection (unless it delegates).
That there are some intermediate modules before things are actually read
from the port is irrelevant -- substitute.scm opened the port, is
responsible for the port and knows best how to handle exceptional
situations involving that port.
Nothing lower-level has the right context/information to make a good
decision on how to handle the exception, so no delegation possible. As
such, guix/scripts/substitute.scm should do it.
It's not 100% clear from the backtrace, but it appears that the
exception (from guix/scripts/substitute.scm perspective) happens at:
;; Procedure: process-substitution
;; Unpack the Nar at INPUT into DESTINATION.
(define cpu-usage
(with-cpu-usage-monitoring
(restore-file hashed destination
#:dump-file (if (and destination-in-store?
deduplicate?)
dump-file/deduplicate*
dump-file))))
This should then be wrapped in an error handler catching 'bad-response',
maybe reporting it, and switching over the next URL.
Greetings,
Maxime.
Debbugs is free software and licensed under the terms of the
GNU Public License version 2. The current version can be
obtained from https://bugs.debian.org/debbugs-source/.