Hi Christopher, Christopher Baines <m...@cbaines.net> writes:
[...] >> Here's a fresh crash (on berlin): >> >> 2023-10-24 06:22:58 GET >> /graphql?query=query%20%7B%0A%20%20issue%28number%3A%2065806%29%20%7B%0A%20%20%20% >> 20open%0A%20%20%7D%0A%7D%0A&variables=%7B%7D 200 >> 2023-10-24 06:22:58 GET /issue/29433/attachment/1/ 200 >> 2023-10-24 06:22:58 GET >> /graphql?query=query%20%7B%0A%20%20issue%28number%3A%2065853%29%20%7B%0A%20%20%20% >> 20open%0A%20%20%7D%0A%7D%0A&variables=%7B%7D 200 >> 2023-10-24 06:22:58 GET >> /graphql?query=query%20%7B%0A%20%20issue%28number%3A%2065869%29%20%7B%0A%20%20%20% >> 20open%0A%20%20%7D%0A%7D%0A&variables=%7B%7D 200 >> 2023-10-24 06:23:15 GET Uncaught exception in task: >> 2023-10-24 06:23:15 In procedure port-auxiliary-write-buffer: Wrong >> type argument in position 1 (expecting >> open port): #<closed: file 7f2ac30077e0> >> 2023-10-24 06:23:15 In fibers.scm: >> 2023-10-24 06:23:15 172:8 6 (_) >> 2023-10-24 06:23:15 In ice-9/boot-9.scm: >> 2023-10-24 06:23:15 1752:10 5 (with-exception-handler _ _ #:unwind? _ # _) >> 2023-10-24 06:23:15 In fibers/web/server.scm: >> 2023-10-24 06:23:15 214:25 4 (_) >> 2023-10-24 06:23:15 In ice-9/suspendable-ports.scm: >> 2023-10-24 06:23:15 83:4 3 (write-bytes #<closed: file 7f2abfe0e770> >> #vu8(47 42 …) …) >> 2023-10-24 06:23:15 In unknown file: >> 2023-10-24 06:23:15 2 (port-write #<closed: file 7f2abfe0e770> >> #vu8(47 42 # …) …) >> 2023-10-24 06:23:15 In ice-9/boot-9.scm: >> 2023-10-24 06:23:15 1685:16 1 (raise-exception _ #:continuable? _) >> 2023-10-24 06:23:15 1685:16 0 (raise-exception _ #:continuable? _) >> 2023-10-24 06:23:15 ice-9/boot-9.scm:1685:16: In procedure raise-exception: >> 2023-10-24 06:23:15 In procedure fport_write: Broken pipe > > I think this is kind of expected. If NGinx hits the proxy_read_timeout > it'll return a 504 to the client and close the connection to Mumi I > think. I think what you're seeing here is Mumi trying to respond to a > request from NGinx that NGinx has closed. If it's expected, we should handle it and produce a useful warning instead of crashing, right? Thanks for tipping in! -- Thanks, Maxim
