That's just a disconnected client. Business as usual when talking overOn 1 November 2013 20:38, Andrei Stebakov <firstname.lastname@example.org> wrote:
> I wonder how do I eliminate this bug:
> [ERROR]] Couldn't write to #<SB-SYS:FD-STREAM
> for "socket
> 127.0.0.1:3001, peer: 127.0.0.1:45338"
> Broken pipe
> It's hard to reproduce it happens on my server ones in a while.
> Is it something fixable? I saw this bug mentioned a long time ago.
> I am using the latest SBCL for linux.
the network. See eg.
Just handle STREAM-ERRORs and you're fine. (A SIMPLE-STREAM-ERROR is a
subclass of STREAM-ERROR. If you need to identify the stream, it is
accessible as STREAM-ERROR-STREAM.)
PS. sbcl-bugs is for reporting bugs in SBCL. For help on using SBCL,
please use sbcl-help.