Hi! Clément Lassieur <clem...@lassieur.org> 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 #<closed: file 3ee3230> #vu8(137 80 78 # …) …) > In unknown file: > 1 (port-write #<closed: file 3ee3230> #vu8(137 80 78 71 …) …) > 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. Ludo’.
