freenode/#shirakumo - IRC Chatlog
Search
12:21:43
Shinmera
Right, so the problem is that it somehow somewhere gets stuck with the pings and pongs, doesn't realise the connection got fucked, and only gets the notification about the broken pipe as soon as someone joins or delivers any kind of update that affects the broken connection one.
13:31:33
Shinmera
Jul 21 15:18:58 fermion sbcl[24849]: 2017-07-21 15:18:58 [TRACE] <LICHAT.SERVER.TCP>: #<CONNECTION Colleen/0>: Waiting for message...
13:31:35
Shinmera
Jul 21 15:18:58 fermion sbcl[24849]: 2017-07-21 15:18:58 [TRACE] <LICHAT.SERVER.TCP>: #<CONNECTION Colleen/0>: Input ready.
13:31:37
Shinmera
Jul 21 15:18:58 fermion sbcl[24849]: 2017-07-21 15:18:58 [TRACE] <LICHAT.SERVER.TCP>: #<CONNECTION Colleen/0>: Waiting for message...
13:31:39
Shinmera
Jul 21 15:18:58 fermion sbcl[24849]: 2017-07-21 15:18:58 [TRACE] <LICHAT.SERVER.TCP>: #<CONNECTION Colleen/0>: Input ready.
13:31:41
Shinmera
Jul 21 15:29:51 fermion sbcl[24849]: 2017-07-21 15:29:51 [TRACE] <LICHAT.SERVER.TCP>: #<SERVER TyNET>: Sending #<LICHAT-PROTOCOL:CONNECTION-UNSTABLE :FROM TyNET :ID 2952017866 :TEXT "Ping idle-timeout of 120 seconds reached."> to #<CONNECTION Colleen/0>
13:33:08
Shinmera
Though that doesn't make sense... since then it wouldn't notice the unstable thing
19:20:53
mood
Shinmera: I'd generally think "opportunistic encryption", like STARTTLS, is a bit of a minefield and thus undesirable. But I don't know particularly much about this stuff