[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: |
Sun, 05 Apr 2015 00:01:56 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) |
address@hidden (Ludovic Courtès) skribis:
> 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.
This was done in d3a6520, so closing this bug.
Ludo’.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#19671: Raw binary data in build log from substitute-binary,
Ludovic Courtès <=