[freenet-support] Freenet 0.7 build 1207 and 1208: DB4O MERGED!

2009-04-11 Thread Matthew Toseland
I released 1207 yesterday, but didn't insert it to the auto-updater. At the 
time new nodes were failing to load any of the default plugins. I discovered 
that there was a bug breaking FCP inserts in 1207, so fixed it and released 
1208, and have now started both inserting to the auto-updater.

Please upgrade! In Freenet 0.7 build 1207, the db4o branch was finally merged 
to stable (please get 1208 because of the above bug). The db4o branch uses a 
database to store the status of persistent requests, radically reducing 
memory usage and making requests resume instantly on startup. Like most big 
database driven projects, this massively overran, taking nearly a year (on 
and off), but it is finally merged now (and fairly stable IMHO). It should 
Just Work, automatically moving your existing queue over, and should be 
reasonably stable, but obviously there are likely to be new bugs, and we'd 
like to hear about them. Also, it is possible that bugs will result in data 
being left over in your node.db4o concerning previous requests; generally 
when this happens there will be ERRORs in the logs (NullPointerException's 
usually); if you are very paranoid this may be a problem for you as db4o does 
not implement any form of garbage collection, so we have to remove the data 
manually and if a bug breaks that, it is possible to leak old data, which 
might conceivably have privacy implications.

Apart from the db4o branch, 1207 also includes various other changes:
- A proper numerical version for plugins, which can be easily compared by the 
node. Most plugins have this new interface, FredPluginRealVersioned.
- This enables us to have minimum versions for each official plugin. Hence 
when you upgrade from a pre-db4o node, some of your old plugins 
(ThawIndexBrowser, KeyExplorer, XMLSpider) will fail to load, but Freenet 
will offer to re-download them for you from the project webserver. (In future 
we will support plugin update over Freenet, this is a step towards it, but 
not yet).
- SSK inserts were sometimes finishing but not completing properly, this may 
have resulted in a very gradual slowdown of the node over time.
- Various bugfixes in fproxy including: preserve ?max-size= through links, 
make the form to restart after a config change work, allow adding more than 
one node at a time on the darknet page.
- Allow docName's within KSKs (that is, allow KSKs to be "directories" - 
KSK at sitename/file-in-site).
- Salted hash datastore (the default): Make sure the datastore config file 
gets written to disk, if it is corrupted on startup create a new one.
- Fix a rare division by zero on the stats page, change the calculation of 
darknet network sizes slightly.
- Fix a bug in the security levels code. (I'm not sure why this didn't happen 
in practice for more people, it shouldn't have a major impact but you may as 
well check that your security levels are set to what you want).
- Fix calculation of how many FEC decode threads to use on Windows.
- Record the ARK number for the opennet noderef to disk when we insert.
- Some minor USK polling changes.
- Show whether a node is a seednode in the FCP commands for listing nodes.
- Various optimisations in the random number generator and other places.
- More unit tests.
- Remove various unused code, other minor internal changes.

Thanks to (I hope I haven't missed anyone out):
j16sdiz
bombe
sashee
infinity0
nextgens
p0s
toad

Meanwhile, Artefact2 has contributed a patch to make XMLSpider (the crawler 
that generates indexes for the search box on the homepage) able to run at 
configurable times of day, and sdiz has made some more minor changes to the 
spider. Zero3 continues his work on the new windows installer, which 
hopefully we will be able to deploy before 0.8, and p0s continues to work on 
Freetalk/WoT, which are rapidly becoming usable.

PLEASE UPGRADE! And if (when?) you find bugs, please report them, ideally to 
the bug tracker, but alternatively to the mailing lists.
https://bugs.freenetproject.org/
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: 



[freenet-support] Freenet 0.7 build 1207 and 1208: DB4O MERGED!

2009-04-11 Thread Matthew Toseland
I released 1207 yesterday, but didn't insert it to the auto-updater. At the 
time new nodes were failing to load any of the default plugins. I discovered 
that there was a bug breaking FCP inserts in 1207, so fixed it and released 
1208, and have now started both inserting to the auto-updater.

Please upgrade! In Freenet 0.7 build 1207, the db4o branch was finally merged 
to stable (please get 1208 because of the above bug). The db4o branch uses a 
database to store the status of persistent requests, radically reducing 
memory usage and making requests resume instantly on startup. Like most big 
database driven projects, this massively overran, taking nearly a year (on 
and off), but it is finally merged now (and fairly stable IMHO). It should 
Just Work, automatically moving your existing queue over, and should be 
reasonably stable, but obviously there are likely to be new bugs, and we'd 
like to hear about them. Also, it is possible that bugs will result in data 
being left over in your node.db4o concerning previous requests; generally 
when this happens there will be ERRORs in the logs (NullPointerException's 
usually); if you are very paranoid this may be a problem for you as db4o does 
not implement any form of garbage collection, so we have to remove the data 
manually and if a bug breaks that, it is possible to leak old data, which 
might conceivably have privacy implications.

Apart from the db4o branch, 1207 also includes various other changes:
- A proper numerical version for plugins, which can be easily compared by the 
node. Most plugins have this new interface, FredPluginRealVersioned.
- This enables us to have minimum versions for each official plugin. Hence 
when you upgrade from a pre-db4o node, some of your old plugins 
(ThawIndexBrowser, KeyExplorer, XMLSpider) will fail to load, but Freenet 
will offer to re-download them for you from the project webserver. (In future 
we will support plugin update over Freenet, this is a step towards it, but 
not yet).
- SSK inserts were sometimes finishing but not completing properly, this may 
have resulted in a very gradual slowdown of the node over time.
- Various bugfixes in fproxy including: preserve ?max-size= through links, 
make the form to restart after a config change work, allow adding more than 
one node at a time on the darknet page.
- Allow docName's within KSKs (that is, allow KSKs to be directories - 
k...@sitename/file-in-site).
- Salted hash datastore (the default): Make sure the datastore config file 
gets written to disk, if it is corrupted on startup create a new one.
- Fix a rare division by zero on the stats page, change the calculation of 
darknet network sizes slightly.
- Fix a bug in the security levels code. (I'm not sure why this didn't happen 
in practice for more people, it shouldn't have a major impact but you may as 
well check that your security levels are set to what you want).
- Fix calculation of how many FEC decode threads to use on Windows.
- Record the ARK number for the opennet noderef to disk when we insert.
- Some minor USK polling changes.
- Show whether a node is a seednode in the FCP commands for listing nodes.
- Various optimisations in the random number generator and other places.
- More unit tests.
- Remove various unused code, other minor internal changes.

Thanks to (I hope I haven't missed anyone out):
j16sdiz
bombe
sashee
infinity0
nextgens
p0s
toad

Meanwhile, Artefact2 has contributed a patch to make XMLSpider (the crawler 
that generates indexes for the search box on the homepage) able to run at 
configurable times of day, and sdiz has made some more minor changes to the 
spider. Zero3 continues his work on the new windows installer, which 
hopefully we will be able to deploy before 0.8, and p0s continues to work on 
Freetalk/WoT, which are rapidly becoming usable.

PLEASE UPGRADE! And if (when?) you find bugs, please report them, ideally to 
the bug tracker, but alternatively to the mailing lists.
https://bugs.freenetproject.org/


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