[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#19671: Raw binary data in build log from substitute-binary
From: |
Ludovic Courtès |
Subject: |
bug#19671: Raw binary data in build log from substitute-binary |
Date: |
Mon, 23 Mar 2015 10:49:42 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) |
This has just happened to me as well, and I think the reason is that,
when a download failure happens (500, 502, 504, etc.), the thread doing
the download directly writes to the current error port.
And as we know, ports are not thread-safe in Guile 2.0 and we’re not
doing additional synchronization here, so everything wrecks havoc.
This is another incentive to merge wip-http-pipelining. I’ll give it
another try.
Thanks,
Ludo’.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#19671: Raw binary data in build log from substitute-binary,
Ludovic Courtès <=