On Monday 14 October 2002 15:37, Marco wrote:
> With several node (513 & 515) when trying to recover a FEC > key, I always have one of this two error > > ==== first type > when pressing start, in few second this message arrive > on upper half screen > > Error sending data to browser: java.lang.NullPointerException > > and this on lower half > Download failed. Couldn't download enough blocks to reconstruct > segment: 0. required: 0 > downloaded: 0 > > > ==== second type > transfert start with the right number of thread, idle > time increment, no single block failed or recovered > > Obviously all nodes works to insert & retrieve normal > keys. > > There is trouble on the FEC decoder ? > > THX. Marco Try this test: 0) Insert a > 1MB file into your local node from the fproxy web interface at at htl 0. 1) Request it from your local node. This works fine on every node I have tested and has worked for at least the last 2 weeks. It's hard for me to figure out what's going on from the limited information in your message. Here's my best guess. I think what is probably happening is that you are requesting a FEC split file that was encoded with an obsolete encoder, fproxy can't get a decoder so treats it as a non-redundant split-file, and hits a bug somewhere in the non-redundant downloading codepath. I'll look into this. If there's a bug I'll clean it up. But the real solution is to get content authors to insert files using the new FEC code. fproxy is using the new code so any FEC files inserted via fproxy should be retrievable by fproxy. fish's FCP based command line tools should be using the new encoders too, though I haven't looked at them lately. --gj _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
