Re: [freenet-support] Freenet 0.7 build 1211, 1212

2009-06-04 Thread Matthew Toseland
On Monday 01 June 2009 22:33:29 SmallSister development wrote:
  Another issue: I have several downloads that report being at 100%,
  but they'll never report completed; even over freenet restarts.
  This could be caused by a freenet crash while in the process of
  writing out the files. (using db4o)
  
  When were they added? If you add a new download for the same key (for
  one of them), do they both complete?
 
 I am still waiting (after more than 24 hours):
   SizeProgress
 New   Unknown 16 (100%??)
 Old   87.1 KiB100%
 
 I started the original downloads somewhere around the 1207, 1208 build
 (not the first distributed build with db4o, but some later build.) There
 are some 470 keys on the download page.

I think this might be a bug recently fixed in git. Please run update.sh testing 
and then add the same key again. What happens to the requests? If you open that 
key in fproxy (without queueing it), does the fetch stall indefinitely? (It 
does in the bug I fixed, which particularly affects XMLSpider). This is caused 
by us mishandling corrupted compressed data...


signature.asc
Description: This is a digitally signed message part.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

Re: [freenet-support] Freenet 0.7 build 1211, 1212

2009-05-30 Thread Matthew Toseland
On Wednesday 27 May 2009 15:41:47 SmallSister development wrote:
 Matthew Toseland wrote:
  Freenet 0.7 build 1212 is now available. Please upgrade.
 [...]
  1212: - Recently we have had several reports of bogus claims by peers
   that the auto-update key has been blown. The nodes would not
  transfer the revocation key, because they didn't have it, they would
  just cause panic. This appears to be a bug or a malicious attack. We
  now give peers a reasonable time to start transferring the
  auto-update revocation key, and if they don't, we cancel the alert
  and let the update through. If 3 of our peers have failed to transfer
  the key, we still treat that as broken.
 
 I had three peers with the message before upgrading to 1211...
 
 Another issue: I have several downloads that report being at 100%, but
 they'll never report completed; even over freenet restarts. This could
 be caused by a freenet crash while in the process of writing out the
 files. (using db4o)

When were they added? If you add a new download for the same key (for one of 
them), do they both complete?


signature.asc
Description: This is a digitally signed message part.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe