public inbox for nncp-devel@lists.cypherpunks.ru
Atom feed

From: John Goerzen <jgoerzen@complete•org>
To: nncp-devel@lists.cypherpunks.ru
Subject: autotoss bug
Date: Thu, 06 May 2021 08:44:24 -0500	[thread overview]
Message-ID: <87fsz0ugcn.fsf@complete.org> (raw)

Hi,

I started trying out -autotoss with nncp-call for the first time 
this week.  I experienced an issue with a set of data piped to 
nncp-exec; an incomplete set of data was sent to the process on 
the receiving side.

I had interrupted nncp-call with Ctrl-C at some point during this 
experimentation, and I also experienced some protocol-related 
hangups from each end, so I am theorizing that nncp-call attempted 
to autotoss an incomplete packet.

I removed -autotoss from the command line, and after the calls 
with the remote eventually concluded, nncp-toss tossed the packet 
correctly (with full data).

The packet was being fed into a command that was able to detect 
the incomplete data and exited with an error code, permitting the 
retries that eventually succeeded.

I've never seen this behavior with regular nncp-toss.

Thanks,

- John

next             reply	other threads:[~2021-05-06 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 13:44 John Goerzen [this message]
2021-05-30 11:42 ` autotoss bug Sergey Matveev