From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Cl=C3=A9ment?= Lassieur Subject: Re: packaging Bootstrap for Cuirass' web interface Date: Mon, 30 Jul 2018 01:45:50 +0200 Message-ID: <87muu9bo7l.fsf@lassieur.org> References: <87zhyitmtc.fsf@lassieur.org> <87pnzetjal.fsf@gnu.org> <87wotmtcks.fsf@lassieur.org> <5b578c0f.1c69fb81.4a8d1.0342@mx.google.com> <87bmawqk4m.fsf@lassieur.org> <87in53ka5r.fsf@lassieur.org> <87fu07k8iv.fsf@lassieur.org> <87a7qeyv3q.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51953) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjvNy-0001G9-5C for guix-devel@gnu.org; Sun, 29 Jul 2018 19:46:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fjvNx-00083j-CW for guix-devel@gnu.org; Sun, 29 Jul 2018 19:46:02 -0400 In-reply-to: <87a7qeyv3q.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Guix-devel , Tatiana Sholokhova Ludovic Court=C3=A8s writes: > Hi! > > Cl=C3=A9ment Lassieur skribis: > >> I also get this if I send many requests at the same time. >> >> Uncaught exception in fiber ##f: >> In ice-9/boot-9.scm: >> 841:4 4 (with-throw-handler _ _ _) >> In web/server/fiberized.scm: >> 2018-07-25T10:33:56 HTTP connection from 127.0.0.1 >> 124:18 3 (_) >> In ice-9/suspendable-ports.scm: >> 83:4 2 (write-bytes # #vu8(137 80 78 # =E2= =80=A6) =E2=80=A6) >> In unknown file: >> 1 (port-write # #vu8(137 80 78 71 =E2= =80=A6) =E2=80=A6) >> In ice-9/boot-9.scm: >> 752:25 0 (dispatch-exception _ _ _) >> ice-9/boot-9.scm:752:25: In procedure dispatch-exception: >> In procedure fport_write: Broken pipe > > That happens if the client sends a request and closes the connection, > and after that the server tries to reply to the client; since the > connection is now closed, the server gets EPIPE. > > In practice this happens in particular when the server takes too much > time to reply and its client has left in the meantime. Oh, got it. Thank you for explaining! Cl=C3=A9ment