public inbox for
Atom feed
* autotoss bug
@ 2021-05-06 13:44 John Goerzen
  2021-05-30 11:42 ` Sergey Matveev
  0 siblings, 1 reply; 2+ messages in thread
From: John Goerzen @ 2021-05-06 13:44 UTC (permalink / raw)
  To: nncp-devel


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.


- John

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-05-30 11:42 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-06 13:44 autotoss bug John Goerzen
2021-05-30 11:42 ` Sergey Matveev