Howdy! Tobias Geerinckx-Rice skribis: > * guix/scripts/substitute.scm (http-multiple-get): Catch BAD-RESPONSE > exceptions and keep going. > --- > > Guix, > > One weird HTTP response from a server will kill ‘guix substitute’: > > updating list of substitutes from 'https://foo'... 50.0%Backtrace: > ... > guix/ui.scm:1229:8: In procedure run-guix-command: > guix/ui.scm:1229:8: Throw to key `bad-response' with args > `("Bad Response-Line: ~s" (""))'. > error: build failed: substituter `substitute' died unexpectedly > > Attached is a patch to ignore such bad responses. The offending .narinfo > will be ignored for that session, and not cached at all. The result: I’m sure you expect this question: what bad responses did you get in practice? :-) Usually that is a sign of a broken HTTP server. Of course it’s widespread enough, we’d better handle it, either in Guix or directly in (web client) in Guile; OTOH, if it’s a genuine problem, we’d better not hide it. Thanks, Ludo’.