On Thursday 24 January 2008 19:56, Robert Hailey wrote: > > On Jan 24, 2008, at 1:33 PM, Matthew Toseland wrote: > > > Lots of these: > > > > Jan 24, 2008 19:32:59:547 (freenet.io.xfer.BlockTransmitter, > > CHKInsert-BackgroundTransfer for -2845527132620253006 to > > 88.169.81.100:51076, > > ERROR): receiver requested block #31 which is not received > > > > Will they go away when 1103 is mandatory? I want to use 1103 as > > alpha 2 since > > it will be well-tested... > > I've noticed these too. Since they appear to be the result of nodes > originating requests w/o starting the transfer, and thus the receiver > timing out and asking for all packets... I *think* that they are fixed > by (r17216). So yes... if they don't cease feel free to mute them.
I don't think so. I'm still getting them. Admittedly 1103 is only just mandatory, some nodes may not have been disconnected yet. But after the errors, I eventually get a successful transfer (allReceived). Okay, there are *two* calls to createMissingPacketNotification: The first is if we get a packetTransmit and it indicates that packets we haven't received have actually been sent. So we need to ask it to resend them. The second is if we get a timeout, and there are still packets we haven't received. This is harmless, it may increase reliability marginally if there are problems with the transport layer, it wastes a few bytes if the transport layer is perfect (which it should be!). Should I take it out? I've silenced the logging anyway. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20080125/ca5926d5/attachment.pgp>
