tested with build 924 now it doesn't throw an npe anymore:
Found new update edition 925 Starting the update process: found the update (925), now fetching it. Starting the update process: found the update (925), now fetching it. Starting the update process: found the update (925), now fetching it. Found 925 Searching for revocation key Revocation counter: 0 Update in progress Cannot update because not running under wrapper 1) but it's showing three times the "starting the update process" line, which looks strange 2) but on the fproxy homepage the warning "A new stable version of Freenet is available" does not disappear anymore 3) there's no feedback to the user that the node won't update because there's no wrapper. perhaps the whole update mechanism should not be shown to the user but a "you could have updated if you had run freenet within the wrapper" >Build 9882 may fix this. Please try it. > >On Thu, Aug 03, 2006 at 06:55:52PM +0200, freenetwork at web.de wrote: >> Found 921 >> Searching for revocation key >> Revocation counter: 0 >> Update in progress >> Exception : java.lang.NullPointerException >> java.lang.NullPointerException >> at freenet.node.updater.NodeUpdater.innerUpdate(NodeUpdater.java:= >219) >> at freenet.node.updater.NodeUpdater.Update(NodeUpdater.java:169) >> at freenet.clients.http.WelcomeToadlet.handlePost(WelcomeToadlet.= >java:80) >> at freenet.clients.http.ToadletContextImpl.handle(ToadletContextI= >mpl.java:295) >> at freenet.clients.http.SimpleToadletServer$SocketHandler.run(Sim= >pleToadletServer.java:342) >> at java.lang.Thread.run(Thread.java:619) >--=20 >Matthew J Toseland - toad at amphibian.dyndns.org >Freenet Project Official Codemonkey - http://freenetproject.org/ >ICTHUS - Nothing is impossible. Our Boss says so.
