On 11/9/26 8:20 AM, Alex Elder wrote:
So the problem occurs when a message arrives that has a bogus
header. We know we received enough bytes to hold a
Sorry, some combination of clicks caused this to send early. I'm
working on a "real" response.
-Alex
