As for this one: Got a trailer chunk ahead of our time!
It seems this is caused by a reestablished session (with that I refer to a connection between peers) where a packet from the previous session with the same peer is considered part of the current session (mux mess). This sometimes causes almost all sessions to be closed and sometimes it is more than one packets from the previous session. This applies to both an inbound session that is closed and opened again by the same peer soon after and an outbound session that is closed and opened again to the same peer soon after. Maybe putting in a longer delay than the constant I saw would be a workable workaround. Is it delayed finalization or some state that remains after a session got closed? -- Vanessa vanessavasquez at fastmail.fm -- http://www.fastmail.fm - Send your email first class
